From: Dave Hansen <dave@linux.vnet.ibm.com>
To: John Stultz <john.stultz@linaro.org>
Cc: linux-kernel@vger.kernel.org, "Arve Hjønnevåg" <arve@android.com>,
"Mel Gorman" <mgorman@suse.de>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: Check if any page in a pageblock is reserved before marking it MIGRATE_RESERVE
Date: Fri, 22 Apr 2011 09:02:10 -0700 [thread overview]
Message-ID: <1303488130.9308.5883.camel@nimitz> (raw)
In-Reply-To: <1303436043-26644-1-git-send-email-john.stultz@linaro.org>
On Thu, 2011-04-21 at 18:34 -0700, John Stultz wrote:
> This fixes a problem where the first pageblock got marked MIGRATE_RESERVE even
> though it only had a few free pages. This in turn caused no contiguous memory
> to be reserved and frequent kswapd wakeups that emptied the caches to get more
> contiguous memory.
This looks sane to me.
Acked-by: Dave Hansen <dave@linux.vnet.ibm.com>
-- Dave
next prev parent reply other threads:[~2011-04-22 16:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 1:34 [PATCH] mm: Check if any page in a pageblock is reserved before marking it MIGRATE_RESERVE John Stultz
2011-04-22 16:02 ` Dave Hansen [this message]
2011-04-26 7:34 ` Mel Gorman
2011-04-26 9:49 ` KOSAKI Motohiro
2011-04-26 10:13 ` Mel Gorman
2011-04-26 17:51 ` John Stultz
-- strict thread matches above, loose matches on Subject: below --
2010-04-05 10:14 [Question] race condition in mm/page_alloc.c regarding page->lru? Mel Gorman
2010-04-06 3:09 ` [PATCH] mm: Check if any page in a pageblock is reserved before marking it MIGRATE_RESERVE Arve Hjønnevåg
2010-04-06 3:09 ` Arve Hjønnevåg
2010-04-06 3:09 ` Arve Hjønnevåg
2010-04-06 4:15 ` Minchan Kim
2010-04-06 4:15 ` Minchan Kim
2010-04-06 4:15 ` Minchan Kim
2010-04-06 15:11 ` Mel Gorman
2010-04-06 15:11 ` Mel Gorman
2010-04-06 15:11 ` Mel Gorman
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=1303488130.9308.5883.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=arve@android.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.