Re: [PATCH v2 0/5] cpumask: cleanup nr_cpu_ids vs nr_cpumask_bits mess
From: Yury Norov
Date: Thu Sep 15 2022 - 10:45:58 EST
On Mon, Sep 05, 2022 at 04:08:15PM -0700, Yury Norov wrote:
> cpumask subsystem uses nr_cpu_ids and nr_cpumask_bits interchangeably
> despite that the variables have different meaning and purpose. It makes
> some cpumask functions broken.
>
> This series cleans that mess and adds new config FORCE_NR_CPUS that
> allows to optimize cpumask subsystem if the number of CPUs is known
> at compile-time.
>
> After some testing I found build broken when SMP is on and NR_CPUS == 1.
> This is addressed in a new patch #1, and in the following patch #2 that
> now declares set_nr_cpu_ids in cpumask.h (was in smp.h).
>
> v1: https://lore.kernel.org/lkml/20220829165748.1008477-1-yury.norov@xxxxxxxxx/T/#mecbd787f8d1bff1454a4ec2fe46ad6dc168df695
> v2:
> - don't declare nr_cpu_ids if NR_CPUS == 1;
> - move set_nr_cpu_ids() from smp.h to cpumask.h to avoid errors in some
> inclusion paths;
> - drop 'default n' in FORCE_NR_CPUS option description;
> - rebase on top of v6.0-rc4.
Any more comments? If not, I'd like to move it into bitmap-for-next.