From: "Luck, Tony" <tony.luck@xxxxxxxxx> Date: Thu, 5 Apr 2007 15:50:02 -0700 > Maybe a granule is not the right unit of allocation ... perhaps 4M > would work better (4M/56 ~= 75000 pages ~= 1.1G)? But if this is > too small, then a hard-coded 16M would be better than a granule, > because 64M is (IMHO) too big. A 4MB chunk of page structs covers about 512MB of ram (I'm rounding up to 64-bytes in my calculations and using an 8K page size, sorry :-). So I think that is too small although on the sparc64 side that is the biggest I have available on most processor models. But I do agree that 64MB is way too big and 16MB is a good compromise chunk size for this stuff. That covers about 2GB of ram with the above parameters, which should be about right. - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
![]() |