On Mon, Mar 6, 2023 at 10:13 AM Vernon Yang <vernon...@gmail.com> wrote:
>
> I also just see nr_cpumask_size exposed to outside, so...
Yeah, it's not great.
nr_cpumask_bits came out of the exact same "this is an internal value
that we use for optimized cpumask accesses", and existed exactly
because it *might* be the same as 'nr_cpu_ids', but it might also be a
simpler "small constant that is big enough" case.
It just depended on the exact kernel config which one was used.
But clearly that internal value then spread outside, and that then
caused problems when the internal implementation changed.
Linus
