On Sun, Dec 28, 2014 at 03:30:23PM -0500, Johannes Weiner wrote: > As such, my proposals would be: > > memory.low: the expected lower end of the workload size > memory.high: the expected upper end > memory.max: the absolute OOM-enforced maximum size > memory.current: the current size > > And then, in the same vein: > > swap.max > swap.current > > These names are short, but they should be unambiguous and descriptive > in their context, and users will have to consult the documentation on > how to configure this stuff anyway.
To me, memory.max resembles memory.max_usage_in_bytes from the old interface, which is confusing. However, if we forget about the old interface, the new names look fine. Thanks, Vladimir -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
