lkml.org 
[lkml]   [2002]   [Jun]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] CONFIG_NR_CPUS, redux
> Ugh let's stop this thread now.  Two points:
>
> (a) imo, the kernel should support out-of-the-box the maximum
> number of CPUs it can handle. Be lucky we now have a
> configure option to change that. But that does not matter..
>
> (b) Right now it is 32. Now you can change it... if you want
> to change the current behavior by _default_ why don't we
> suggest that _after_ this is accepted into 2.5? I.e., one
> battle at a time.

Indeed. And before that gets changed, it would be necessary
to change the bootstrap procedure not to crash if you have
more than NR_CPUS cpus (as Andrew reported it did), but instead
to just not configure them ... much less troublesome.

M.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:26    [W:0.061 / U:8.360 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site