From: Dave Hansen <haveblue@us.ibm.com>
To: Paul Jackson <pj@sgi.com>
Cc: Anton Blanchard <anton@samba.org>, Andrew Morton <akpm@osdl.org>,
Simon.Derr@bull.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>,
IWAMOTO Toshihiro <iwamoto@valinux.co.jp>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: [Patch 4/4] cpusets top mask just online, not all possible
Date: Sat, 11 Sep 2004 10:39:32 -0700 [thread overview]
Message-ID: <1094924372.3997.16.camel@localhost> (raw)
In-Reply-To: <20040911100731.2f400271.pj@sgi.com>
Now that I've actuallly _looked_ at your code, I noticed that the
mems_allowed really is just a nodemask_t.
So, you shouldn't have much to worry about from the current memory
hotplug stuff because we don't mess with hotplugging actual NUMA nodes
yet. As I eluded to before, you might need notification of we ever get
down to a zero-sized node, but that should be id. You'll certainly need
notification when entire nodes go offline, so I'm adding Martin Bligh to
the cc list (we just talked about NUMA hotplug yesterday).
Martin, you might want to look back in your LKML archives for where this
discussion came from.
-- Dave
next prev parent reply other threads:[~2004-09-11 17:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 8:28 [Patch 0/4] four small cpuset patches Paul Jackson
2004-09-11 8:28 ` [Patch 1/4] cpusets display allowed masks in proc status Paul Jackson
2004-09-11 8:28 ` [Patch 2/4] cpusets simplify cpus_allowed setting in attach Paul Jackson
2004-09-11 8:28 ` [Patch 3/4] cpusets remove useless validation check Paul Jackson
2004-09-11 8:28 ` [Patch 4/4] cpusets top mask just online, not all possible Paul Jackson
2004-09-11 14:10 ` Anton Blanchard
2004-09-11 17:07 ` Paul Jackson
2004-09-11 17:28 ` Dave Hansen
2004-09-12 2:21 ` Paul Jackson
2004-09-12 4:43 ` Dave Hansen
2004-09-12 5:35 ` Paul Jackson
2004-09-12 5:42 ` Paul Jackson
2004-09-11 17:39 ` Dave Hansen [this message]
2004-09-11 18:55 ` Andi Kleen
2004-09-12 2:29 ` Paul Jackson
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=1094924372.3997.16.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=Simon.Derr@bull.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=iwamoto@valinux.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=pj@sgi.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