On 06/20/2011 01:34 PM, Cong Wang wrote:
Even if it is really 10K, why not save it since it doesn't much effort to make this. ;) Not only memory, but also time, this could also save a little time to initialize the kernel. For me, the more serious thing is the logic, there is no way to totally disable it as long as I have THP in .config currently. This is why I said the design is broken.
There are many things you cannot totally disable as long as they are enabled in the .config. Think about things like swap, or tmpfs - neither of which you are going to use in the crashdump kernel. I believe we need to keep the kernel optimized for common use and convenience. Crashdump is very much a corner case. Yes, using less memory in crashdump is worthwhile, but lets face it - the big memory user there is likely to be the struct page array, with everything else down in the noise... -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>