From: Mitch Adair <mitch@theneteffect.com>
To: cw@f00f.org (Chris Wedgwood)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CPU hot swap for 2.4.3 + s390 support
Date: Sat, 5 May 2001 11:34:16 -0500 (CDT) [thread overview]
Message-ID: <200105051634.LAA02026@mako.theneteffect.com> (raw)
In-Reply-To: <20010506033746.A30690@metastasis.f00f.org> from "Chris Wedgwood" at May 06, 2001 03:37:46 AM
> 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.
Wouldn't that be lot of the same issues as a "swapoff" with some portion of
that in use? (except for the kernel data case of course...)
M
next prev parent reply other threads:[~2001-05-05 16:35 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 [this message]
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
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=200105051634.LAA02026@mako.theneteffect.com \
--to=mitch@theneteffect.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.