mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
	kernel list <linux-kernel@vger.kernel.org>,
	andrea@suse.de, npiggin@suse.de
Subject: Re: min_free_kbytes documentation, /proc/sys/vm docs
Date: Mon, 13 Aug 2007 16:12:31 +0200	[thread overview]
Message-ID: <20070813141231.GA9834@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <1187013180.20108.59.camel@twins>

Hi!

> > min_free_kbytes documentation says:
> > 
> > min_free_kbytes:
> > 
> > This is used to force the Linux VM to keep a minimum number 
> > of kilobytes free.  The VM uses this number to compute a pages_min
> > value for each lowmem zone in the system.  Each lowmem zone gets 
> > a number of reserved free pages based proportionally on its size.
> > 
> > ....which is not too helpful :-(. In particular, should kernel survive
> > setting this to 0 and still work reliably? IOW is this
> > performance-only tweak, or does it correctness implications?
> 
> correctness
> 
> sort-of, since PF_MEMALLOC usage is currently un-bounded.

/me is scared. If this is for correctness... why is it different on
different machines? Should we specify some minimum value in the
documentation?

> > I guess it should also say something like "do not set this to more
> > than half of your physical RAM (or half of lowmem?) or you get an
> > instant OOM".
> 
> yeah, lowmem, not sure on the oom part, it should work with quite high
> limits, although I've never tried it with ridiculous numbers.

I did, and it indeed OOMs instantly.

Perhaps something like this should be applied?

Signed-off-by: Pavel Machek <pavel@suse.cz>

diff --git a/Documentation/sysctl/vm.txt b/Documentation/sysctl/vm.txt
index a0ccc5b..e460c19 100644
--- a/Documentation/sysctl/vm.txt
+++ b/Documentation/sysctl/vm.txt
@@ -111,6 +111,12 @@ of kilobytes free.  The VM uses this num
 value for each lowmem zone in the system.  Each lowmem zone gets 
 a number of reserved free pages based proportionally on its size.
 
+Some minimal ammount of memory is needed to satisfy PF_MEMALLOC
+allocations; if you set this to lower than 1024KB, your system will
+become subtly broken, and prone to deadlock under high loads.
+
+Setting this too high will OOM your machine instantly.
+
 ==============================================================
 
 percpu_pagelist_fraction

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2007-08-13 15:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13 13:46 Pavel Machek
2007-08-13 13:53 ` Peter Zijlstra
2007-08-13 14:12   ` Pavel Machek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070813141231.GA9834@atrey.karlin.mff.cuni.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®