linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Who's doing what with cpu/memory/node hotplug?
Date: Thu, 13 May 2004 14:00:45 +0000	[thread overview]
Message-ID: <20040513140044.GA14588@sgi.com> (raw)
In-Reply-To: <20040512205107.16bb82a6.pj@sgi.com>

On Wed, May 12, 2004 at 09:23:35PM -0700, Dave Hansen wrote:
> 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.

Where can I find a copy of the latest CONFIG_NONLINEAR patch? I recall
one that was posted by Dave McCracken in early Apr. Is that the one I should
review?

When we did the initial implementation of CONFIG_DISCONTIGMEM, we
looked briefly at the CONFIG_NONLINEAR patch (or idea) that was
floating around at that time. The patch may have changed so some of 
my initial concerns may no longer apply, but the early patch would
not have performed very well on the SGI hardware. 

The SGI architecture has an absurdly sparse address space. The smallest
memory block is 64MB but the max physical address is 49 bits (500TB).  
IIRC, this resulted in some very large tables used to convert between 
logical & physical addresses. Because of the size of these tables, cache
misses would be common on references to these tables. Is this still a 
valid concern???

Anyway, I'd like to study the latest patch & see how well it would work on our
hardware......


-- 
Thanks

Jack Steiner (steiner@sgi.com)          651-683-5302
Principal Engineer                      SGI - Silicon Graphics, Inc.




-------------------------------------------------------
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

  parent reply	other threads:[~2004-05-13 14:00 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
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 [this message]
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=20040513140044.GA14588@sgi.com \
    --to=steiner@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 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).