> It only affects hot paths in the NUMA case so non-NUMA users will not care.
For x86-64 most distribution kernels are NUMA these days. > For NUMA users, I have posted patches that eliminate multiple zonelists > altogether which will reduce cache footprint (something like 7K per node on > x86_64) How do you get to 7k? We got worst case 3 zones node (normally less); that's three pointers per GFP level. > and make things like MPOL_BIND behave in a consistent manner. That > would cost on CPU but save on cache which would (hopefully) result in a net > gain in most cases. That might be a good tradeoff, but without seeing the patch the 7k number sounds very dubious. > I would like to go with this patch for now just for policies but for > 2.6.23, we could leave it as "policies only apply to ZONE_MOVABLE when it > is used" if you really insisted on it. It's less than ideal though for > sure. Or disable ZONE_MOVABLE. It seems to be clearly not well thought out well yet. Perhaps make it dependent on !CONFIG_NUMA. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
