* H. Peter Anvin <h...@zytor.com> wrote: > On 11/03/2013 07:57 AM, Josh Boyer wrote: > > > > OK, that makes sense. So in this scenario, we could probably either: > > > > a) do away with MAXSMP entirely and just depend on > > CONFIG_CPUMASK_OFFSTACK. > > > > b) make MAXSMP something even higher than 4096. Like 5120 or 6144, etc. > > > > Which would you prefer? Either is easy enough to code up, I just need > > to know which I should shoot for. > > > > Let's get rid of MAXSMP.
I'd rather not, because it has caught a number of regressions in the past, because randconfig can wander over it and trigger those large configs. randconfig will not randomize numeric Kconfig ranges, so there's no other mechanism right now to trigger those large config kernels. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/