[PATCH 0/8] v2 De-Couple sysfs memory directories from memory sections

Kay Sievers kay.sievers at vrfy.org
Wed Sep 29 23:39:58 EST 2010

On Wed, Sep 29, 2010 at 14:37, Greg KH <greg at kroah.com> wrote:
> On Wed, Sep 29, 2010 at 10:32:34AM +0200, Avi Kivity wrote:
>>  On 09/29/2010 04:50 AM, Greg KH wrote:
>>> >
>>> >  Because the old ABI creates 129,000+ entries inside
>>> >  /sys/devices/system/memory with their associated links from
>>> >  /sys/devices/system/node/node*/ back to those directory entries.
>>> >
>>> >  Thankfully things like rpm, hald, and other miscellaneous commands scan
>>> >  that information.
>>> Really?  Why?  Why would rpm care about this?  hald is dead now so we
>>> don't need to worry about that anymore,
>> That's not what compatiblity means.  We can't just support
>> latest-and-greatest userspace on latest-and-greatest kernels.
> Oh, I know that, that's not what I was getting at at all here, sorry if
> it came across that way.
> I wanted to know so we could go fix programs that are mucking around in
> these files, as odds are, the shouldn't be doing that in the first
> place.
> Like rpm, why would it matter what the memory in the system looks like?

HAL does many inefficient things, but I don't think it's using
/sys/system/, besides that it may check the cpufreq govenors state


More information about the Linuxppc-dev mailing list