Re: percpu memory setup and num_possible_cpus() vs. nr_cpu_ids
- From: Tejun Heo <teheo@xxxxxxxxxx>
- Date: Fri, 29 May 2009 09:38:06 +0900
Hello, Jan.
Jan Beulich wrote:
Tejun,
this code of yours, as I learned the hard way during some Xen kernel work,
assumes that cpu_possible_map is not sparse. While on native x86 this is
certainly true, I wonder whether such a dependency should really exist in
architecture neutral code. Below, for reference, the places I needed to
change (4k allocator only). However, there are more instances of this in the
other allocators - those seem more problematic, as they directly drive input
to alloc_bootmem() (hence a lot of memory could be wasted, or allocation
could even fail, with a very sparse cpu_possible_map if one would simply
also use nr_cpu_ids here). In the remap (x86 - under the assumption that
if this change gets made, it should also be made in x86 code, albeit not
directly affected) allocator's case things may not be that bad, since the
memory gets freed again at the end of setup_pcpu_remap().
There's other related larger issue. It looks like possible but
offline configuration can be quite common with virtualization and
allocating for all possible cpus on boot can waste problematic amount
of space, so the plan is to allocate only for online cpus on boot and
allocate the rest as cpus come online. This will require audit of
percpu users and probably a new cpumask representing cpus which have
ever been up.
The issue you're describing should be solved when the above is
implemented, right?
Thanks.
--
tejun
--
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/
- Follow-Ups:
- Re: percpu memory setup and num_possible_cpus() vs. nr_cpu_ids
- From: Jan Beulich
- Re: percpu memory setup and num_possible_cpus() vs. nr_cpu_ids
- References:
- percpu memory setup and num_possible_cpus() vs. nr_cpu_ids
- From: Jan Beulich
- percpu memory setup and num_possible_cpus() vs. nr_cpu_ids
- Prev by Date: Re: [PATCH RFC] v7 expedited "big hammer" RCU grace periods
- Next by Date: Xen is a feature
- Previous by thread: percpu memory setup and num_possible_cpus() vs. nr_cpu_ids
- Next by thread: Re: percpu memory setup and num_possible_cpus() vs. nr_cpu_ids
- Index(es):
Relevant Pages
|