mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: Robert Picco <Robert.Picco@hp.com>, linux-kernel@vger.kernel.org
Cc: colpatch@us.ibm.com, mbligh@aracnet.com
Subject: Re: boot time node and memory limit options
Date: Tue, 16 Mar 2004 09:43:29 -0800	[thread overview]
Message-ID: <20040316174329.GA29992@sgi.com> (raw)
In-Reply-To: <4057392A.8000602@hp.com>

On Tue, Mar 16, 2004 at 12:28:10PM -0500, Robert Picco wrote:
> This patch supports three boot line options.  mem_limit limits the
> amount of physical memory.  node_mem_limit limits the amount of
> physical memory per node on a NUMA machine.  nodes_limit reduces the
> number of NUMA nodes to the value specified.  On a NUMA machine an
> eliminated node's CPU(s) are removed from the cpu_possible_map.  
> 
> The patch has been tested on an IA64 NUMA machine and uniprocessor X86
> machine.

I think this patch will be really useful.  Matt and Martin, does it look
ok to you?  Given that discontiguous support is pretty platform specific
right now, I thought it might be less code if it was done in arch/, but
a platform independent version is awfully nice...

Thanks,
Jesse

       reply	other threads:[~2004-03-16 17:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4057392A.8000602@hp.com>
2004-03-16 17:43 ` Jesse Barnes [this message]
2004-03-16 19:39   ` Martin J. Bligh
2004-03-17 16:15     ` Robert Picco
2004-03-17 16:36       ` Martin J. Bligh
2004-03-17 17:09         ` Dave Hansen
2004-03-17 17:51           ` Jesse Barnes
2004-03-17 18:12             ` Dave Hansen
2004-03-17 19:30         ` Robert Picco
2004-03-17 19:44           ` Martin J. Bligh
2004-03-17 20:01             ` Robert Picco
2004-03-17 20:58               ` Martin J. Bligh
2004-03-17 20:52             ` Dave Hansen
2004-03-16 17:07 Robert Picco
2004-03-16 17:34 ` Randy.Dunlap
     [not found] ` <16471.48076.447058.132559@napali.hpl.hp.com>
2004-03-17 18:07   ` Robert Picco

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=20040316174329.GA29992@sgi.com \
    --to=jbarnes@sgi.com \
    --cc=Robert.Picco@hp.com \
    --cc=colpatch@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    /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
all inboxes | Powered by JetHome®