From: David Rientjes <rientjes@google.com>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, benh@kernel.crashing.org,
sparclinux@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch 1/6] sparc: remove dependency on __GFP_NOFAIL
Date: Wed, 21 Jul 2010 02:41:03 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1007210237500.19769@chino.kir.corp.google.com> (raw)
In-Reply-To: <20100720.203100.254885062.davem@davemloft.net>
On Tue, 20 Jul 2010, David Miller wrote:
> > The kmalloc() in mdesc_kmalloc() is failable, so remove __GFP_NOFAIL from
> > its mask.
> >
> > Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > Signed-off-by: David Rientjes <rientjes@google.com>
>
> The __GFP_NOFAIL is there intentionally.
>
> The code above this, in the cases where the machine description is
> dynamically updated by the hypervisor at run time, long after boot,
> has no failure handling.
>
> We absolutely must accept the machine descriptor update and fetch it
> from the hypervisor into a new buffer.
>
> Please don't remove this.
>
Ok, fair enough. I was convinced by the error handling in both
mdesc_update() and mdesc_kmallloc() that this was a failable allocation,
but I understand how mdesc_update() must succeed given your description.
We can remove those branches from those two functions, though, since
__GFP_NOFAIL will always succeed before returning.
I'm planning on replacing __GFP_NOFAIL with a __GFP_KILLABLE flag that
will use all of the page allocator's capabilities (direct reclaim, memory
compaction for order > 0, and the oom killer) before failing. Then,
existing __GFP_NOFAIL users can use
do {
page = alloc_page(GFP_KERNEL | __GFP_KILLABLE);
} while (!page);
to remove several branches from the page allocator that we'll no longer
need. I'll do this in phase two and make sure to convert this instance to
do that.
Thanks!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-07-21 9:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 2:44 [patch 0/6] remove dependency on __GFP_NOFAIL for failable allocations David Rientjes
2010-07-21 2:44 ` [patch 1/6] sparc: remove dependency on __GFP_NOFAIL David Rientjes
2010-07-21 3:31 ` David Miller
2010-07-21 9:41 ` David Rientjes [this message]
2010-07-21 2:44 ` [patch 2/6] infiniband: " David Rientjes
2010-07-21 3:19 ` Steve Wise
2010-07-21 17:55 ` Roland Dreier
2010-07-21 2:45 ` [patch 3/6] fs: " David Rientjes
2010-07-23 19:36 ` Andrew Morton
2010-07-23 19:51 ` David Rientjes
2010-07-23 21:12 ` Pekka Enberg
2010-07-21 2:45 ` [patch 4/6] gfs2: " David Rientjes
2010-07-21 9:24 ` Steven Whitehouse
2010-07-21 9:31 ` David Rientjes
2010-07-21 2:45 ` [patch 6/6] jbd2: " David Rientjes
2010-07-22 14:14 ` Ted Ts'o
2010-07-22 18:09 ` David Rientjes
2010-07-22 23:09 ` Ted Ts'o
2010-07-22 23:24 ` David Rientjes
2010-07-23 14:10 ` Ted Ts'o
2010-07-23 14:57 ` Jan Kara
2010-07-23 15:05 ` Ted Ts'o
2010-07-23 15:32 ` Jan Kara
2010-07-23 19:40 ` David Rientjes
2010-07-23 19:52 ` Ted Ts'o
2010-07-21 19:26 ` [patch 5/6] jbd: " David Rientjes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1007210237500.19769@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linux-mm@kvack.org \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox