From: Mel Gorman <mel@csn.ul.ie>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: stable@kernel.org, linux-kernel@vger.kernel.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Frans Pop <elendil@planet.nl>, Jiri Kosina <jkosina@suse.cz>,
Sven Geggus <lists@fuchsschwanzdomain.de>,
Karol Lewandowski <karol.k.lewandowski@gmail.com>,
Tobias Oetiker <tobi@oetiker.ch>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Rik van Riel <riel@redhat.com>,
Christoph Lameter <cl@linux-foundation.org>,
Stephan von Krawczynski <skraw@ithnet.com>,
"Kernel Testers List <kernel-testers@vger.kernel.org>,
Mel Gorman <mel@csn.ul.ie>"@linux-foundation.org
Subject: Re: [PATCH 2/3] page allocator: Do not allow interrupts to use ALLOC_HARDER
Date: Wed, 28 Oct 2009 10:24:13 +0000 [thread overview]
Message-ID: <20091028102413.GR8900@csn.ul.ie> (raw)
In-Reply-To: <20091027130924.fa903f5a.akpm@linux-foundation.org>
On Tue, Oct 27, 2009 at 01:09:24PM -0700, Andrew Morton wrote:
> On Tue, 27 Oct 2009 13:40:32 +0000
> Mel Gorman <mel@csn.ul.ie> wrote:
>
> > Commit 341ce06f69abfafa31b9468410a13dbd60e2b237 altered watermark logic
> > slightly by allowing rt_tasks that are handling an interrupt to set
> > ALLOC_HARDER. This patch brings the watermark logic more in line with
> > 2.6.30.
> >
> > [rientjes@google.com: Spotted the problem]
> > Signed-off-by: Mel Gorman <mel@csn.ul.ie>
> > Reviewed-by: Pekka Enberg <penberg@cs.helsinki.fi>
> > Reviewed-by: Rik van Riel <riel@redhat.com>
> > Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> > ---
> > mm/page_alloc.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> > index dfa4362..7f2aa3e 100644
> > --- a/mm/page_alloc.c
> > +++ b/mm/page_alloc.c
> > @@ -1769,7 +1769,7 @@ gfp_to_alloc_flags(gfp_t gfp_mask)
> > * See also cpuset_zone_allowed() comment in kernel/cpuset.c.
> > */
> > alloc_flags &= ~ALLOC_CPUSET;
> > - } else if (unlikely(rt_task(p)))
> > + } else if (unlikely(rt_task(p)) && !in_interrupt())
> > alloc_flags |= ALLOC_HARDER;
> >
> > if (likely(!(gfp_mask & __GFP_NOMEMALLOC))) {
>
> What are the runtime-observeable effects of this change?
>
A reduction of high-order GFP_ATOMIC allocation failures reported
http://www.gossamer-threads.com/lists/linux/kernel/1144153
> The description is a bit waffly-sounding for a -stable backportable
> thing, IMO. What reason do the -stable maintainers and users have to
> believe that this patch is needed, and an improvement?
>
Allocation failure reports are occuring against 2.6.31.4 that did not
occur in 2.6.30. The bug reporter observes no such allocation failures
with this and the previous patch applied. The data is fuzzier than I'd
like but both patches do appear to be required.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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:[~2009-10-28 10:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 13:40 [PATCH 0/3] Reduce GFP_ATOMIC allocation failures, partial fix V3 Mel Gorman
2009-10-27 13:40 ` [PATCH 1/3] page allocator: Always wake kswapd when restarting an allocation attempt after direct reclaim failed Mel Gorman
2009-10-27 13:40 ` [PATCH 2/3] page allocator: Do not allow interrupts to use ALLOC_HARDER Mel Gorman
[not found] ` <1256650833-15516-3-git-send-email-mel-wPRd99KPJ+uzQB+pC5nmwQ@public.gmane.org>
2009-10-27 20:09 ` Andrew Morton
2009-10-27 21:12 ` David Rientjes
2009-10-31 18:40 ` Pavel Machek
2009-10-31 19:51 ` David Rientjes
2009-10-31 20:11 ` Pavel Machek
2009-10-31 21:19 ` David Rientjes
2009-10-31 22:29 ` Pavel Machek
2009-10-31 22:55 ` Rik van Riel
2009-11-01 7:35 ` Pavel Machek
2009-11-01 12:37 ` KOSAKI Motohiro
2009-11-01 14:44 ` Rik van Riel
2009-11-01 19:32 ` Pavel Machek
2009-11-02 16:38 ` Christoph Lameter
2009-10-31 23:59 ` Rik van Riel
2009-11-02 16:42 ` Christoph Lameter
2009-11-02 20:53 ` David Rientjes
2009-11-03 17:10 ` Christoph Lameter
2009-11-04 1:46 ` David Rientjes
2009-11-04 9:01 ` Pavel Machek
2009-11-09 10:11 ` Mel Gorman
2009-10-28 10:24 ` Mel Gorman [this message]
2009-10-27 13:40 ` [PATCH 3/3] vmscan: Force kswapd to take notice faster when high-order watermarks are being hit Mel Gorman
2009-10-27 18:18 ` Rik van Riel
2009-10-27 20:19 ` Andrew Morton
2009-10-28 3:54 ` KOSAKI Motohiro
2009-10-28 10:29 ` Mel Gorman
2009-10-28 19:47 ` Andrew Morton
2009-11-02 16:05 ` Mel Gorman
2009-11-02 17:32 ` Frans Pop
2009-11-02 17:38 ` Mel Gorman
2009-11-02 20:36 ` Mel Gorman
2009-11-03 22:01 ` Frans Pop
2009-11-03 22:08 ` Mel Gorman
2009-11-04 0:01 ` Frans Pop
2009-11-04 1:18 ` Mel Gorman
2009-11-04 2:05 ` Frans Pop
2009-11-04 2:08 ` Frans Pop
2009-11-04 15:48 ` Mel Gorman
2009-11-04 20:57 ` Frans Pop
2009-11-05 16:48 ` [PATCH 3/3] vmscan: Force kswapd to take notice faster when high-order watermarks are being hit (data on latencies available) Mel Gorman
2009-11-12 11:36 ` Frans Pop
2009-11-04 2:08 ` [PATCH 3/3] vmscan: Force kswapd to take notice faster when high-order watermarks are being hit Mel Gorman
2009-10-28 13:02 ` [PATCH 0/3] Reduce GFP_ATOMIC allocation failures, partial fix V3 Karol Lewandowski
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=20091028102413.GR8900@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc="Kernel Testers List <kernel-testers@vger.kernel.org>, Mel Gorman <mel@csn.ul.ie>"@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=elendil@planet.nl \
--cc=jkosina@suse.cz \
--cc=karol.k.lewandowski@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lists@fuchsschwanzdomain.de \
--cc=penberg@cs.helsinki.fi \
--cc=riel@redhat.com \
--cc=skraw@ithnet.com \
--cc=stable@kernel.org \
--cc=tobi@oetiker.ch \
/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