From: Andrew Morton <akpm@linux-foundation.org>
To: Andy Whitcroft <apw@shadowen.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mel Gorman <mel@csn.ul.ie>
Subject: Re: [PATCH 3/3] introduce HIGH_ORDER delineating easily reclaimable orders
Date: Sat, 21 Apr 2007 01:32:10 -0700 [thread overview]
Message-ID: <20070421013210.1bed9ceb.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070421012843.f5a814eb.akpm@linux-foundation.org>
On Sat, 21 Apr 2007 01:28:43 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> It would have been better to have patched page_alloc.c independently, then
> to have used HIGH_ORDER in "lumpy: increase pressure at the end of the inactive
> list".
Actually that doesn't matter, because I plan on lumping all the lumpy patches
together into one lump.
I was going to duck patches #2 and #3, such was my outrage. But given that
it's all lined up to be a single patch, followup cleanup patches will fit in
OK. Please.
--
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:[~2007-04-21 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 15:03 [PATCH 0/3] Lumpy Reclaim V6 Andy Whitcroft
2007-04-20 15:03 ` [PATCH 1/3] kswapd: use reclaim order in background reclaim Andy Whitcroft
2007-04-20 15:04 ` [PATCH 2/3] lumpy: increase pressure at the end of the inactive list Andy Whitcroft
2007-04-21 8:24 ` Andrew Morton
2007-04-20 15:04 ` [PATCH 3/3] introduce HIGH_ORDER delineating easily reclaimable orders Andy Whitcroft
2007-04-21 8:28 ` Andrew Morton
2007-04-21 8:32 ` Andrew Morton [this message]
2007-04-23 10:23 ` Andy Whitcroft
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=20070421013210.1bed9ceb.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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