Re: [Lhms-devel] RE: memory hotremove prototype, take 3
From: Yasunori Goto
Date: Wed Dec 03 2003 - 16:28:55 EST
> > 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
My understanding is that the kernel and device drivers sometimes
assume physical memory address is not changed.
For example, IA32 kernel often uses __PAGE_OFFSET.
I suppose that there are many case which the kernel and device drivers
assume physical address is not changed like this.
Even if we use Mr. Iwamoto's method use, some memories will remain.
But, if remaining memories will be on only one (or a few) node,
other nodes will be able to be hot-removed.
I think that dividing attribute hotpluggable or not is realistic way.
> (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).
Mr. Iwamoto and Mr. Takahashi told me that some memories which is used
by NFS are especially difficult to be hotplugged....
Yasunori Goto <ygoto at fsw.fujitsu.com>
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/