From: Peter Zijlstra <peterz@infradead.org>
To: Pavel Machek <pavel@ucw.cz>
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 15:53:00 +0200 [thread overview]
Message-ID: <1187013180.20108.59.camel@twins> (raw)
In-Reply-To: <20070813134626.GA7305@atrey.karlin.mff.cuni.cz>
On Mon, 2007-08-13 at 15:46 +0200, Pavel Machek wrote:
> 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.
> 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.
next prev parent reply other threads:[~2007-08-13 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 13:46 min_free_kbytes documentation, /proc/sys/vm docs Pavel Machek
2007-08-13 13:53 ` Peter Zijlstra [this message]
2007-08-13 14:12 ` Pavel Machek
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=1187013180.20108.59.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=pavel@ucw.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.