linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Who's doing what with cpu/memory/node hotplug?
Date: Thu, 13 May 2004 04:23:35 +0000	[thread overview]
Message-ID: <1084422215.974.25.camel@nighthawk> (raw)
In-Reply-To: <20040512205107.16bb82a6.pj@sgi.com>

On Wed, 2004-05-12 at 20:51, Paul Jackson wrote:
> Could someone explain to me who's doing what with cpu, memory and node
> hotplug?
>
> And I also just noticed the thread on lkml by Keiichiro, with comments
> from Dave, mentioning Matthew, hinting at additional interactions that
> might be desirable between various efforts here.  I even see some SGI
> work here. 

I'm working on a little corner of memory hotplug: resizing existing
zones.  I'll be doing it on hardware that is both NUMA and flat SMP
systems, with no removal of entire NUMA nodes, at least not yet.  

We've decided to use CONFIG_NONLINEAR, which has been discussed quite a
bit before.  It allows you to take discontiguous, nonlinear physical
memory, and rearrange it so that it can be managed in linear pieces. 
Basically, this lets us keep the struct zone virtually unchanged because
we can map any physical memory to any pfn that we like (in certain size
sections, of course).  This is done for x86, and we're working on
ppc64.  This code has the potential to replace much of
CONFIG_DISCONTIGMEM.

The second bit of work that I have my eyes on are the sysfs interfaces
which will end up being the hotplug memory API to userspace.  I hope to
keep these as simple as possible inside the kernel, exposing enough
information to userspace that it can do most of the work.  For instance,
I certainly hope that an offline procedure for an entire node would
consist of more than one call into the kernel.  offline each memory
section ... offline each cpu ... offline the struct node ...

Although I haven't thought about it much, I would imagine that most of
the node hotplug work will involve very similar operations to the cpu
hotplug work: going through all of the for_each_node() loops and adding
some locking along with some node_possible() vs. node_online() checks.  

-- Dave



-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2004-05-13  4:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13  3:51 Who's doing what with cpu/memory/node hotplug? Paul Jackson
2004-05-13  4:23 ` Dave Hansen [this message]
2004-05-13  4:44 ` Ashok Raj
2004-05-13  4:59 ` Paul Jackson
2004-05-13  6:35 ` Keiichiro Tokunaga
2004-05-13  6:50 ` Dave Hansen
2004-05-13  7:18 ` Paul Jackson
2004-05-13 14:00 ` Jack Steiner
2004-05-13 16:01 ` Dave Hansen
2004-05-13 16:33 ` Jack Steiner
2004-05-14  1:14 ` Keiichiro Tokunaga
2004-05-14 13:49 ` Russ Anderson

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=1084422215.974.25.camel@nighthawk \
    --to=haveblue@us.ibm.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;
as well as URLs for NNTP newsgroup(s).