Re: [PATCH 3/4] cpumask: use maxcpus=NUM to extend the cpu limitas well as restrict the limit

From: Mike Travis
Date: Fri Dec 12 2008 - 10:38:49 EST


Rusty Russell wrote:
> On Thursday 11 December 2008 21:58:09 Mike Travis wrote:
>> Impact: allow adding additional cpus.
>>
>> Use maxcpus=NUM kernel parameter to extend the number of possible cpus as well
>> as (currently) limit them. Any cpus >= number of present cpus will disabled.
> ...
>
> These two bits of logic are very similar: can we merge them?
>
...

Since there's already precedence for "possible_cpus=XXX" might that be a better
alternative? In which case maxcpus does not need to change at all.

Thanks,
Mike
--
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/