From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: CPU only nodes (no memory) patch for NUMA/DISCONTIG
Date: Tue, 24 Feb 2004 21:54:45 +0000 [thread overview]
Message-ID: <16443.51237.413077.809134@napali.hpl.hp.com> (raw)
In-Reply-To: <403A583C.7010808@hp.com>
>>>>> On Tue, 24 Feb 2004 09:40:49 -0500, Robert Picco <Robert.Picco@hp.com> said:
Robert> Added commentary here. There are additional comments in code which
Robert> hopefully elucidates the algorithm.
Robert> Also I've addressed the other feedback.
The patch looked fine to me. The only changes I made is to squish the
remaining trailing whitespace (which was only on otherwise empty
lines, in your case) and to change "CPU only" to "CPU-only" (seems
easier to parse that way). I cooked up a ChangeLog entry, but in the
future, I'd really appreciate it if all patch-submissions would always
include the desired ChangeLog. Otherwise, I have to go digging
through old mail and that takes time and makes it likely that I'll get
something wrong. I attached the ChangeLog entry below. If you want
something corrected, let me know soon, while I can still edit it.
Thanks,
--david
ChangeSet@1.1666, 2004-02-24 13:48:30-08:00, Robert.Picco@hp.com
[PATCH] ia64: add support for NUMA machines with CPU-only (memory-less) nodes
This patch works around a limitation in the current NUMA code, which
doesn't support CPU-only (memory-less) nodes. With this patch
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.
prev parent reply other threads:[~2004-02-24 21:54 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
2004-02-24 14:40 ` Robert Picco
2004-02-24 21:54 ` David Mosberger [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=16443.51237.413077.809134@napali.hpl.hp.com \
--to=davidm@napali.hpl.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