> Bah! I'm at a competitive disadvantage because I've got a lesser
> BITS_PER_LONG. No matter, NR_CPUS > BITS_PER_LONG shall be conquered
> and the explosion of kernel threads will be quite visible (though
> unfortunately probably post-freeze).
Speaking of which, the recent CONFIG_NR_CPUS addition shows just how
bloated all our [NR_CPU] structures are. We need to get serious about
using the per cpu data stuff. Going from 32 to 64 was over 500kB on my
ppc64 build.
Anton
-
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/
This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:42 EST