Add a tunable that decides when memory should be compacted and when it should be reclaimed
in [Kernel]
|
Prev: Allow CONFIG_MIGRATION to be set without CONFIG_NUMA or memory hot-remove
Next: linux-next: manual merge of the v4l-dvb tree with Linus' tree
From: Andrew Morton on 6 Apr 2010 20:10 On Fri, 2 Apr 2010 17:02:46 +0100 Mel Gorman <mel(a)csn.ul.ie> wrote: > The kernel applies some heuristics when deciding if memory should be > compacted or reclaimed to satisfy a high-order allocation. One of these > is based on the fragmentation. If the index is below 500, memory will > not be compacted. This choice is arbitrary and not based on data. To > help optimise the system and set a sensible default for this value, this > patch adds a sysctl extfrag_threshold. The kernel will only compact > memory if the fragmentation index is above the extfrag_threshold. Was this the most robust, reliable, no-2am-phone-calls thing we could have done? What about, say, just doing a bit of both until something worked? For extra smarts we could remember what worked best last time, and make ourselves more likely to try that next time. Or whatever, but extfrag_threshold must die! And replacing it with a hardwired constant doesn't count ;) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |