Re: [PATCH] Correct nr_processes() when CPUs have been unplugged
From: Christoph Lameter
Date: Tue Nov 03 2009 - 19:27:30 EST
On Tue, 3 Nov 2009, Ingo Molnar wrote:
> Sidenote: percpu areas currently are kept allocated on x86.
They must be kept allocated for all possible cpus. Arch code cannot decide
to not allocate per cpu areas.
Search for "for_each_possible_cpu" in the source tree if you want more
> That might change in the future though, especially with virtual systems
> where the possible range of CPUs can be very high - without us
> necessarily wanting to pay the percpu area allocation price for it. I.e.
> dynamic deallocation of percpu areas is something that could happen in
> the future.
Could be good but would not be as easy as you may think since core code
assumes that possible cpus have per cpu areas configured. There will be
the need for additional notifiers and more complex locking if we want to
have percpu areas for online cpus only. Per cpu areas are permanent at
this point which is a good existence guarantee that avoids all sorts of
> Nice one. I'm wondering why it was not discovered for such a long time.
Cpu hotplug is rarely used (what you listed are rare and unusual cases)
and therefore online cpus == possible cpus == present cpus.
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/