From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Mel Gorman <mel@skynet.ie>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
Date: Tue, 5 Dec 2006 11:25:41 -0800 [thread overview]
Message-ID: <20061205112541.2a4b7414.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612050754560.11213@schroedinger.engr.sgi.com>
On Tue, 5 Dec 2006 08:00:39 -0800 (PST)
Christoph Lameter <clameter@sgi.com> wrote:
> On Mon, 4 Dec 2006, Andrew Morton wrote:
>
> > > > What happens when we need to run reclaim against just a section of a zone?
> > > > Lumpy-reclaim could be used here; perhaps that's Mel's approach too?
> > >
> > > Why would we run reclaim against a section of a zone?
> >
> > Strange question. Because all the pages are in use for something else.
>
> We always run reclaim against the whole zone not against parts. Why
> would we start running reclaim against a portion of a zone?
Oh for gawd's sake.
If you want to allocate a page from within the first 1/4 of a zone, and if
all those pages are in use for something else then you'll need to run
reclaim against the first 1/4 of that zone. Or fail the allocation. Or
run reclaim against the entire zone. The second two options are
self-evidently dumb.
--
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:[~2006-12-05 19:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 17:07 Mel Gorman
2006-12-01 1:31 ` Andrew Morton
2006-12-01 9:54 ` Mel Gorman
2006-12-01 19:01 ` Andrew Morton
2006-12-04 14:07 ` Mel Gorman
2006-12-04 19:30 ` Andrew Morton
2006-12-04 19:41 ` Christoph Lameter
2006-12-04 20:06 ` Andrew Morton
2006-12-04 20:17 ` Christoph Lameter
2006-12-04 21:19 ` Andrew Morton
2006-12-04 21:43 ` Christoph Lameter
2006-12-04 22:22 ` Andrew Morton
2006-12-05 16:00 ` Christoph Lameter
2006-12-05 19:25 ` Andrew Morton [this message]
2006-12-05 20:01 ` Christoph Lameter
2006-12-05 21:47 ` Mel Gorman
2006-12-05 23:33 ` Christoph Lameter
2006-12-06 9:31 ` Mel Gorman
2006-12-06 17:31 ` Christoph Lameter
2006-12-08 1:21 ` Jeremy Fitzhardinge
2006-12-08 2:20 ` Christoph Lameter
2006-12-08 6:11 ` Jeremy Fitzhardinge
2006-12-05 18:10 ` Mel Gorman
2006-12-04 20:34 ` Mel Gorman
2006-12-04 22:34 ` Andrew Morton
2006-12-04 23:45 ` Mel Gorman
2006-12-05 1:16 ` KAMEZAWA Hiroyuki
2006-12-05 10:03 ` Mel Gorman
2006-12-05 16:05 ` Christoph Lameter
2006-12-05 18:26 ` Andrew Morton
2006-12-05 19:59 ` Christoph Lameter
2006-12-05 16:14 ` Christoph Lameter
2006-12-05 17:17 ` Mel Gorman
2006-12-05 19:54 ` Christoph Lameter
2006-12-05 15:52 ` Andy Whitcroft
2006-12-05 15:48 ` Andy Whitcroft
2006-12-04 20:37 ` Peter Zijlstra
2006-12-06 14:18 ` 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=20061205112541.2a4b7414.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.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