public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Keiichiro Tokunaga <tokunaga.keiich@jp.fujitsu.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	hotplug devel <linux-hotplug-devel@lists.sourceforge.net>,
	lhns-devel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] [PATCH] Node Hotplug Support
Date: Wed, 12 May 2004 19:04:47 -0700	[thread overview]
Message-ID: <1084413887.974.7.camel@nighthawk> (raw)
In-Reply-To: <20040513102751.48c61d48.tokunaga.keiich@jp.fujitsu.com>

On Wed, 2004-05-12 at 18:27, Keiichiro Tokunaga wrote:
> On Sun, 09 May 2004 22:45:42 -0700
> Dave Hansen <haveblue@us.ibm.com> wrote:
> 
> > On Sun, 2004-05-09 at 18:47, Keiichiro Tokunaga wrote:
> > > There is no NUMA support in the current code yet.  I'll post a
> > > rough patch to show my idea soon.  I'm thinking to regard a
> > > container device that has PXM as a NUMA node so far.
> > 
> > Don't you think it would be a good idea to work with some of the current
> > code, instead of trying to wrap around it?  
> 
> Are you saying that LHNS should use the current NUMA code
> (or coming code in the future) to support NUMA node hotplug?

Absolutely.  Why do we need wrappers when we can offline entire nodes
with 6-line shell scripts?  The CPU hotplug interfaces are here today
and the memory stuff will be here soon.  Perhaps you could help with the
NUMA part.

#!/bin/sh
NODENUM=$1
NODEDIR=/sys/devices/system/node/node${NODENUM}
for i in $NODEDIR/cpu* $NODEDIR/memory*; do
	echo 0 > $i/control/online
fi
echo 0 > $NODEDIR/control/online

We don't currently export bus to node mappings in sysfs, but we have
them in the kernel, so that won't be too hard to export as well.  

-- Dave


  reply	other threads:[~2004-05-13  2:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07 15:39 [ANNOUNCE] [PATCH] Node Hotplug Support Keiichiro Tokunaga
2004-05-07 15:49 ` Dave Hansen
2004-05-10  1:47   ` Keiichiro Tokunaga
2004-05-10  2:12     ` [Lhns-devel] " Takayoshi Kochi
2004-05-10 11:20       ` Keiichiro Tokunaga
2004-05-10  5:45     ` Dave Hansen
2004-05-13  1:27       ` Keiichiro Tokunaga
2004-05-13  2:04         ` Dave Hansen [this message]
2004-05-13  6:35           ` Keiichiro Tokunaga
2004-05-13  6:45             ` Dave Hansen
2004-05-13  6:54               ` [Lhns-devel] " Dave Hansen
2004-05-14  1:13               ` Keiichiro Tokunaga
2004-05-14  1:21                 ` Dave Hansen
2004-05-07 16:16 ` [ANNOUNCE] [PATCH] " Martin J. Bligh
2004-05-10  2:03   ` Keiichiro Tokunaga
     [not found] <1TfLX-4M4-9@gated-at.bofh.it>
2004-05-07 19:10 ` Andi Kleen
2004-05-08 18:00   ` Ingo Oeser
2004-05-10  2:17   ` Keiichiro Tokunaga
2004-05-10 19:54     ` Andi Kleen

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=1084413887.974.7.camel@nighthawk \
    --to=haveblue@us.ibm.com \
    --cc=lhns-devel@lists.sourceforge.net \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tokunaga.keiich@jp.fujitsu.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