cpumask: Use nr_cpu_ids in seq_cpumask
authorRusty Russell <rusty@rustcorp.com.au>
Mon, 29 Dec 2008 22:35:19 +0000 (09:05 +1030)
committerRusty Russell <rusty@rustcorp.com.au>
Mon, 29 Dec 2008 22:35:19 +0000 (09:05 +1030)
commite12f0102ac81d660c9f801d0a0e10ccf4537a9de
tree00463d0a0e3978d21a1c29331b58f101a2b50adf
parentcbe31f02f5b5536f17dd978118e25052af528071
cpumask: Use nr_cpu_ids in seq_cpumask

Impact: cleanup, futureproof

nr_cpu_ids is the (badly named) runtime limit on possible CPU numbers;
ie. the variable version of NR_CPUS.

With the new cpumask operators, only bits less than this are defined.
So we should use it everywhere, rather than NR_CPUS.  Eventually this
will make it possible to allocate cpumasks of the minimal length at runtime.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Mike Travis <travis@sgi.com>
Acked-by: Ingo Molnar <mingo@elte.hu>
include/linux/seq_file.h