public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Picco <bob.picco@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] memory less nodes
Date: Fri, 06 May 2005 10:41:51 +0000	[thread overview]
Message-ID: <20050506104151.GI17548@localhost.localdomain> (raw)
In-Reply-To: <20050505152826.GF17548@localhost.localdomain>

Greg Edwards wrote:	[Thu May 05 2005, 11:17:31PM EDT]
> On Thu, May 05, 2005 at 11:28:26AM -0400, Bob Picco wrote:
> | Tony,
> | 
> | I reworked how nodes with only CPUs are treated.  The patch below seems
> | simpler to me and has eliminated the complicated routine
> | reassign_cpu_only_nodes.  There isn't any longer the requirement
> | to modify ACPI NUMA information which was in large part the
> | complexity introduced in reassign_cpu_only_nodes. 
> | 
> | This patch will produce a different number of nodes. For example,
> | reassign_cpu_only_nodes would reduce two CPUonly nodes and one memory node
> | configuration to one memory+CPUs node configuration.  This patch
> | doesn't change the number of nodes which means the user will see three.  Two
> | nodes without memory and one node with all the memory.
> | 
> | While doing this patch, I noticed that early_nr_phys_cpus_node isn't serving
> | any useful purpose.  It is called once in find_pernode_space but the value
> | isn't used to computer pernode space.  
> 
> FWIW, I tried this patch out on a couple different Altix configurations,
> and didn't see any problems with it.
> 
> Greg
> -
Thanks.  I was hoping for this to happen.

I removed Jesse from cc: list after discovering last night that he is no
longer at SGI.

bob

      parent reply	other threads:[~2005-05-06 10:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 15:28 [PATCH] memory less nodes Bob Picco
2005-05-06  3:17 ` Greg Edwards
2005-05-06 10:41 ` Bob Picco [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=20050506104151.GI17548@localhost.localdomain \
    --to=bob.picco@hp.com \
    --cc=linux-ia64@vger.kernel.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