[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100415061200.GC21517@alberich.amd.com>
Date: Thu, 15 Apr 2010 08:12:00 +0200
From: Andreas Herrmann <herrmann.der.user@...glemail.com>
To: Christoph Lameter <cl@...ux-foundation.org>,
Lee Schermerhorn <Lee.Schermerhorn@...com>
Cc: Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
Greg Kroah-Hartman <gregkh@...e.de>,
linux-kernel@...r.kernel.org
Subject: useless node/has_cpu sysfs attribute
Hi,
commit 99dcc3e5a94ed491fbef402831d8c0bbb267f995 (this_cpu: Page
allocator conversion) removed the call
node_set_state(node, N_CPU); /* this node has a cpu */
(in fact process_zones() where this call happened was removed).
Thus the sysfs attribute /sys/devices/system/node/has_cpu doesn't
show anything anymore.
Before this commit the attribute usually listed all nodes ("having a CPU")
in the system, e.g.
worms linux # cat /sys/devices/system/node/has_cpu
0-7
This attribute never reflected any changes triggered by CPU hotplug.
I.e. you could set all CPUs of a node offline but the node still was listed
in this attribute. (because no hotplug notifiers exist that would
call node_set_state(node, N_CPU)/node_clear_state(node,N_CPU)).
Do we need this attribute?
Who relies on information from this attribute?
I think if we do not need the attribute we should remove it. But if
there is use for it we need to fix it and make it CPU hotplug aware.
Opinions?
Thanks,
Andreas
PS: The attribute was introduced with commit
bde631a51876f23e9bbdce43f02b7232502c151e (mm: add node states sysfs
class attributeS)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists