From: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
To: "Yasunori Goto" <ygoto@fsw.fujitsu.com>, "Pavel Machek" <pavel@suse.cz>
Cc: <linux-kernel@vger.kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
"IWAMOTO Toshihiro" <iwamoto@valinux.co.jp>,
"Hirokazu Takahashi" <taka@valinux.co.jp>,
"Linux Hotplug Memory Support" <lhms-devel@lists.sourceforge.net>
Subject: RE: memory hotremove prototype, take 3
Date: Tue, 2 Dec 2003 21:19:02 -0800 [thread overview]
Message-ID: <A20D5638D741DD4DBAAB80A95012C0AE0125DCB0@orsmsx409.jf.intel.com> (raw)
> From: Yasunori Goto
> IMHO, To hot-remove memory, memory attribute should be divided
> into Hotpluggable and no-Hotpluggable, and each attribute memory
> should be allocated each unit(ex. node).
Why? I still don't get that -- we should be able to use the virtual
addressing mechanism of any CPU to swap under the rug any virtual
address without needing to do anything more than allocate a page frame
for the new physical location (I am ignoring here devices that are
directly accessing physical memory--a callback in the device model could
be added to require them to reallocate their buffers).
Or am I deadly and naively wrong?
Iñaky Pérez-González -- Not speaking for Intel -- all opinions are my own (and my fault)
next reply other threads:[~2003-12-03 5:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 5:19 Perez-Gonzalez, Inaky [this message]
2003-12-03 21:23 ` [Lhms-devel] RE: memory hotremove prototype, take 3 Yasunori Goto
-- strict thread matches above, loose matches on Subject: below --
2003-12-10 0:45 Luck, Tony
2003-12-03 17:57 Luck, Tony
2003-12-01 20:12 Luck, Tony
2003-12-02 3:01 ` IWAMOTO Toshihiro
2003-12-02 6:43 ` Hirokazu Takahashi
2003-12-02 22:26 ` Yasunori Goto
2003-12-01 3:41 IWAMOTO Toshihiro
2003-12-01 19:56 ` Pavel Machek
2003-12-03 19:41 ` Martin J. Bligh
2003-12-04 3:58 ` IWAMOTO Toshihiro
2003-12-04 5:38 ` Martin J. Bligh
2003-12-04 15:44 ` IWAMOTO Toshihiro
2003-12-04 17:12 ` Martin J. Bligh
2003-12-04 18:27 ` Jesse Barnes
2003-12-04 18:29 ` Martin J. Bligh
2003-12-04 18:59 ` Jesse Barnes
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=A20D5638D741DD4DBAAB80A95012C0AE0125DCB0@orsmsx409.jf.intel.com \
--to=inaky.perez-gonzalez@intel.com \
--cc=iwamoto@valinux.co.jp \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=taka@valinux.co.jp \
--cc=tony.luck@intel.com \
--cc=ygoto@fsw.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;
as well as URLs for NNTP newsgroup(s).