On Fri, Feb 12, 2010 at 01:34:40PM -0500, Valdis.Kletnieks@xxxxxx wrote: > On Fri, 12 Feb 2010 12:00:53 GMT, Mel Gorman said: > > This patch adds a proc file /proc/sys/vm/compact_memory. When an arbitrary > > value is written to the file, all zones are compacted. The expected user > > of such a trigger is a job scheduler that prepares the system before the > > target application runs. > > Argh. A global trigger in /proc, and a per-node trigger in /sys too. Can we > get by with just one or the other? Should the /proc one live in /sys too? > The sysfs trigger is only visible on NUMA. The proc one is easier to use when the requirement is "compact all memory". There doesn't appear to be a suitable place in sysfs for the proc trigger as it's already the case that all proc tunables are not reflected in sysfs. -- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>