From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Yasunori Goto <y-goto@jp.fujitsu.com>,
Christoph Lameter <clameter@sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: Trying to make use of hotplug memory for xen balloon driver
Date: Fri, 28 Mar 2008 11:21:16 -0700 [thread overview]
Message-ID: <1206728476.7883.133.camel@nimitz.home.sr71.net> (raw)
In-Reply-To: <47EC1E75.6090102@goop.org>
On Thu, 2008-03-27 at 15:23 -0700, Jeremy Fitzhardinge wrote:
> If the user does a mass online via /sys the system explodes because it
> onlines a large number of pages which have no backing memory. Since
> none of those pages can be mapped, the kernel explodes in a variety of
> interesting ways.
Yeah, it does look like you need some kind of partial onlining.
> So I'd really like to inhibit the sysfs interface on these sections.
> Thoughts?
The balloon driver isn't an exact fit for memory hotplug as it stands,
so there are going to be a few growing pains here. :)
I'm not sure just inhibiting sysfs is the best thing. What would you
think about adding partial sections, initializing the 'struct page's,
but just not touching the memory?
-- Dave
next prev parent reply other threads:[~2008-03-28 18:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 23:11 Jeremy Fitzhardinge
2008-03-27 0:09 ` Dave Hansen
2008-03-27 0:15 ` Jeremy Fitzhardinge
2008-03-27 1:23 ` Christoph Lameter
2008-03-27 0:26 ` Dave Hansen
2008-03-27 22:23 ` Jeremy Fitzhardinge
2008-03-28 18:21 ` Dave Hansen [this message]
2008-03-27 0:50 ` KAMEZAWA Hiroyuki
2008-03-27 5:57 ` Jeremy Fitzhardinge
2008-03-27 6:11 ` KAMEZAWA Hiroyuki
2008-03-27 6:09 ` Jeremy Fitzhardinge
2008-03-27 20:54 ` Jeremy Fitzhardinge
2008-03-28 0:20 ` KAMEZAWA Hiroyuki
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=1206728476.7883.133.camel@nimitz.home.sr71.net \
--to=dave@linux.vnet.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=chrisw@sous-sol.org \
--cc=clameter@sgi.com \
--cc=jeremy@goop.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=y-goto@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
all inboxes | Powered by JetHome®