>> Increase the generic ia64 config from its current max of 512 CPUs to a >> new max of 1024 CPUs. > >I wonder why this would be seen as a sane thing... >Very few people have 1024 cpus, and the ones that do sure would know how >to set 1024 in their kernel config. In fact I would argue to lower it. I >can see the point of keeping it over 64, to give the >more-cpus-than-a-long code more testing, but 512 is too high already.. >most people who have ia64 will not have 512 cpus. Would it be impossibly hard to make the >64 cpus case (when the code switches from a single word to an array) be dependent on a boot-time variable? If we could, then the defconfig could just say 128, and users of monster machines would just boot with "maxcpus=4096" to increase the size of the bitmask arrays. -Tony - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Sat Jan 07 04:24:25 2006
This archive was generated by hypermail 2.1.8 : 2006-01-07 04:24:33 EST