From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: CPU only nodes (no memory) patch for NUMA/DISCONTIG
Date: Mon, 23 Feb 2004 21:36:49 +0000 [thread overview]
Message-ID: <20040223213649.GA8680@sgi.com> (raw)
In-Reply-To: <403A583C.7010808@hp.com>
On Mon, Feb 23, 2004 at 02:45:00PM -0500, Robert Picco wrote:
> David:
>
> Jesse has reviewed this for me and we are in agreement. CPU only nodes
> are moved to a node with memory which is at the closest relative
> distance per the SLIT information. Any node reassignments will result
> in the compression of the nodes and renumbering the nid values where
> appropriate.
I really just reviewed the feature, I think it actually ends up being a
little better (or at least easier to get right) for situations where a
node has CPUs but no memory than the early bootmem scheme I was
proposing. I haven't looked at the code much though (aside from asking
for a function comment and DECLARE_BITMAP usage), so I'm not sure about
that part of it...
> There is hope our firmware folks will handle interleaved memory
> correctly in regards to SLIT and PXM. There should be more data on this
> later in the week. No matter what the outcome of a firmware change,
> the patch will work.
Cool, keep us posted.
> /*
> + * This function will move nodes with only CPUs (no memory)
> + * to a node with memory which is at the minimum numa_slit distance.
> + * Any reassigments will result in the compression of the nodes
> + * and renumbering the nid values where appropriate.
> + */
May as well use the kdoc style function comment here, just to be
consistent with the rest of the file (it's documented somewhere in
Documentation/kernel-doc-nano-HOWTO.txt).
Thanks,
Jesse
next prev parent reply other threads:[~2004-02-23 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 19:45 CPU only nodes (no memory) patch for NUMA/DISCONTIG Robert Picco
2004-02-23 21:16 ` David Mosberger
2004-02-23 21:36 ` Jesse Barnes [this message]
2004-02-24 14:40 ` Robert Picco
2004-02-24 21:54 ` David Mosberger
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=20040223213649.GA8680@sgi.com \
--to=jbarnes@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.