Re: [Lhms-devel] Re: [PATCH] ACPI based Memory Hotplug Driver Patch

[Dave Hansen <haveblue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>]

On Tue, 2004-09-14 at 02:29, Keiichiro Tokunaga wrote:
> On Mon, 13 Sep 2004 21:11:44 -0700 Dave Hansen wrote:
> > What I want is to make sure that any hotplug memory application that is
> > written can use the same directories no matter whether it is a ppc
> > machine using OpenFirmware or an x86/ia64 machine using ACPI.  
> 
> That's an ideal solution that I like:)
> 
> > Instead of just laying thing out in firmware/acpi, can we have another
> > directory that mirrors this information in the system/devices/
> > directory, but is identical across architectures?  
> 
> That's an interesting idea.  I think that not all of the stuffs could
> be identical across architectures, so we would lay architecture
> specific sutffs only in architecture specific directory (e.g. /sys/firmware/acpi/),
> and general stuffs (like physical address) in both the archtecture
> specific directory and the mirror directory.  This sounds reasonable
> to me.  By the way, where do you think would be a candidate for
> the mirror directory?

Well, in retrospect, I think that /sys/devices/system/memory is probably
a bad place for the hotplug controls to go.  It's really just a logical
view of the memory from Linux's perspective, and that somewhat takes a
back seat to the physical layout presented by the hardware.

So, perhaps the physical layout should go in /sys/devices/system/memory,
and we can put the hotplug controls in
/sys/devices/system/logical/memory, or something similar.  

-- Dave



-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m