cpumask: prepare for iterators to only go to nr_cpu_ids/nr_cpumask_bits: net
In future all cpumask ops will only be valid (in general) for bit numbers < nr_cpu_ids. So use that instead of NR_CPUS in iterators and other comparisons. This is always safe: no cpu number can be >= nr_cpu_ids, and nr_cpu_ids is initialized to NR_CPUS at boot. Signed-off-by:Rusty Russell <rusty@rustcorp.com.au> Signed-off-by:
Mike Travis <travis@sgi.com> Acked-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
David S. Miller <davem@davemloft.net>
Showing
- net/core/neighbour.c 2 additions, 2 deletionsnet/core/neighbour.c
- net/ipv4/netfilter/nf_conntrack_l3proto_ipv4_compat.c 2 additions, 2 deletionsnet/ipv4/netfilter/nf_conntrack_l3proto_ipv4_compat.c
- net/ipv4/route.c 2 additions, 2 deletionsnet/ipv4/route.c
- net/netfilter/nf_conntrack_standalone.c 2 additions, 2 deletionsnet/netfilter/nf_conntrack_standalone.c
Loading
Please register or sign in to comment