From: Peter Rival <frival@zk3.dec.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Anton Blanchard <anton@samba.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CPU hot swap for 2.4.3 + s390 support
Date: Sat, 05 May 2001 20:08:59 -0400 [thread overview]
Message-ID: <3AF4961B.F23C9948@zk3.dec.com> (raw)
In-Reply-To: <20010505063726.A32232@va.samba.org> <3AF4118F.330C3E86@zk3.dec.com> <20010506033746.A30690@metastasis.f00f.org>
Chris Wedgwood wrote:
> On Sat, May 05, 2001 at 10:43:27AM -0400, Peter Rival wrote:
>
> Has anyone looked into memory hot swap/hot add support?
>
> Adding memory probably isn't going to be too hard... but taking
> existing memory off line is tricky. You have to find some way of
> finding all the pages that are in use and then dealing with them
> appropriately, and when some are locked or contain kernel data this
> would be extremely difficult I should think.
>
Hrmm... I agree this is a hard problem. I know people smarter than I have
been thinking about this type of problem at Compaq. While I haven't talked to
them directly, my only guess would be that we'd have to hand-rewrite some page
tables after copying the page contents to a new area. It's late Saturday and
I really haven't thought this through fully, so I'm not even sure that would
work, but it's something like how we support replicated text segments on our
GS series...don't know why it wouldn't work here. *shrug*
> Especially with systems with Chipkill coming out, this would be
> great to support...
>
> Chipkill?
>
It's the IBM technology that works around bad memory by detecting single-bit
errors and removing the chip that caused it from use. I'd think of this as a
big hammer version of that in software. Besides, eventually you'll want to
replace the DIMM that has the bad chip, and what better way then while the
system is still running (as long as it's stable, of course ;) I'm just
thinking out loud, so someone can correct me if I'm being loopy...
- Pete
next prev parent reply other threads:[~2001-05-06 0:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 13:37 [PATCH] CPU hot swap for 2.4.3 + s390 support Anton Blanchard
2001-05-05 14:43 ` Peter Rival
2001-05-05 15:37 ` Chris Wedgwood
2001-05-05 16:34 ` Mitch Adair
2001-05-06 1:53 ` Chris Wedgwood
2001-05-06 2:24 ` Rik van Riel
2001-05-06 2:19 ` Rik van Riel
2001-05-06 0:08 ` Peter Rival [this message]
2001-05-06 2:02 ` Chris Wedgwood
2001-05-06 2:19 ` Rik van Riel
2001-05-06 2:25 ` Chris Wedgwood
2001-05-06 2:31 ` Rik van Riel
2001-05-06 15:38 ` David Woodhouse
2001-05-06 8:03 ` Aaron Lehmann
2001-05-06 8:43 ` Stephen Beynon
2001-05-06 7:15 ` Dwayne C. Litzenberger
2001-05-06 8:04 ` Aaron Lehmann
2001-05-06 17:06 ` Ben Ford
2001-05-07 1:42 ` Jakob Østergaard
2001-05-05 20:49 ` Bruce Harada
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=3AF4961B.F23C9948@zk3.dec.com \
--to=frival@zk3.dec.com \
--cc=anton@samba.org \
--cc=cw@f00f.org \
--cc=linux-kernel@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