On Fri, 18 Oct 2013 14:56:59 +0200 Jerome Marchand <jmarc...@redhat.com> wrote:
> Some applications that run on HPC clusters are designed around the > availability of RAM and the overcommit ratio is fine tuned to get the > maximum usage of memory without swapping. With growing memory, the 1% > of all RAM grain provided by overcommit_ratio has become too coarse > for these workload (on a 2TB machine it represents no less than > 20GB). > > This patch adds the new overcommit_ratio_ppm sysctl variable that > allow to set overcommit ratio with a part per million precision. > The old overcommit_ratio variable can still be used to set and read > the ratio with a 1% precision. That way, overcommit_ratio interface > isn't broken in any way that I can imagine. The way we've permanently squished this mistake in the past is to switch to "bytes". See /proc/sys/vm/*bytes. Would that approach work in this case? -- 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/
