From: mel@skynet.ie (Mel Gorman)
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH] 2.6.23-rc1-mm1 - fix missing numa_zonelist_order sysctl
Date: Thu, 2 Aug 2007 17:18:29 +0100 [thread overview]
Message-ID: <20070802161829.GB22493@skynet.ie> (raw)
In-Reply-To: <20070802161437.GA22493@skynet.ie>
On (02/08/07 17:14), Mel Gorman didst pronounce:
> On (02/08/07 09:44), KAMEZAWA Hiroyuki didst pronounce:
> > On Wed, 01 Aug 2007 15:02:51 -0400
> > Lee Schermerhorn <Lee.Schermerhorn@hp.com> wrote:
> > > [But, maybe reordering the zonelists is not such a good idea
> > > when ZONE_MOVABLE is populated?]
> > >
> >
> > It's case-by-case I think. In zone order with ZONE_MOVABLE case,
> > user's page cache will not use ZONE_NORMAL until ZONE_MOVABLE in all node
> > is exhausted. This is an expected behavior, I think.
> >
>
> This is expected behaviour. I see no reason for lower zones to be used
> for allocations that use memory from a higher zone with free memory.
>
Bah. I should have thought of this better.
If you are using ZONE_MOVABLE and the zonelist is in zone order, one would
use memory from remote nodes when suitable local memory was available. I don't
have a quick answer on how this should be handled. The answer may be
something like;
o When ordering zonelists by nodes, order them so that the movable zone
is paired with the next highest zones in a zonelist before moving to the
next node
> > I think the real problem is the scheme for "How to set zone movable size to
> > appropriate value for the system". This needs more study and documentation.
> > (but maybe depends on system configuration to some extent.)
> >
>
> It depends on the system configuration and the workload requirements.
> Right now, there isn't exact information available on what size the zone
> should be. It'll need to be studied over a period of time.
>
> --
> 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>
--
--
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>
prev parent reply other threads:[~2007-08-02 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 19:02 Lee Schermerhorn
2007-08-02 0:44 ` KAMEZAWA Hiroyuki
2007-08-02 15:07 ` Lee Schermerhorn
2007-08-03 0:27 ` KAMEZAWA Hiroyuki
2007-08-02 16:14 ` Mel Gorman
2007-08-02 16:18 ` Mel Gorman [this message]
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=20070802161829.GB22493@skynet.ie \
--to=mel@skynet.ie \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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