LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mel@skynet.ie>, Andi Kleen <ak@suse.de>,
	Lee.Schermerhorn@hp.com, kamezawa.hiroyu@jp.fujitsu.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Apply memory policies to top two highest zones when highest zone is ZONE_MOVABLE
Date: Tue, 7 Aug 2007 13:37:24 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708071334430.3430@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070807111430.f35c03c0.akpm@linux-foundation.org>

On Tue, 7 Aug 2007, Andrew Morton wrote:

> > It's even more constrained than that. It only applies to the MPOL_BIND
> > policy when kernelcore= is specified. The other policies work the same
> > as they ever did.
> 
> so.. should we forget about merging the horrible-hack?

Support MPOL_BIND is a basic NUMA feature. This is going to make .23 
unusable for us if kernelcore= is used. If we cannot use kernelcore then 
NUMA systems cannot use the features that depend on kernelcore.




  reply	other threads:[~2007-08-07 20:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02 17:21 Mel Gorman
2007-08-02 19:41 ` Lee Schermerhorn
2007-08-02 20:45 ` Christoph Lameter
2007-08-06 19:44   ` Andrew Morton
2007-08-06 20:13     ` Christoph Lameter
2007-08-06 21:56   ` Paul Jackson
2007-08-03 22:02 ` Andi Kleen
2007-08-04  0:23   ` Mel Gorman
2007-08-04  8:51     ` Andi Kleen
2007-08-04 16:39       ` Mel Gorman
2007-08-06 19:15   ` Andrew Morton
2007-08-06 19:18     ` Christoph Lameter
2007-08-06 20:31     ` Andi Kleen
2007-08-06 21:55       ` Mel Gorman
2007-08-07  5:12         ` Andrew Morton
2007-08-07 16:55           ` Mel Gorman
2007-08-07 18:14             ` Andrew Morton
2007-08-07 20:37               ` Christoph Lameter [this message]
2007-08-08 16:49               ` Mel Gorman
2007-08-08 17:03                 ` Christoph Lameter
2007-08-06 21:48     ` Mel Gorman
2007-08-06 22:31       ` Christoph Lameter
2007-08-06 22:57         ` 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=Pine.LNX.4.64.0708071334430.3430@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@skynet.ie \
    --subject='Re: [PATCH] Apply memory policies to top two highest zones when highest zone is ZONE_MOVABLE' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).