linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Shewmaker <agshew@gmail.com>
To: Simon Jeons <simon.jeons@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	alan@lxorguk.ukuu.org.uk, ric.masonn@gmail.com
Subject: Re: [PATCH v7 2/2] mm: replace hardcoded 3% with admin_reserve_pages knob
Date: Mon, 8 Apr 2013 12:49:25 -0600	[thread overview]
Message-ID: <CAF-E8XHnTTUPm1s5RF2wEC-sjt3wYDhLgj__UQRz-b6AyC++vQ@mail.gmail.com> (raw)
In-Reply-To: <5160C244.6080807@gmail.com>

On Sat, Apr 6, 2013 at 6:48 PM, Simon Jeons <simon.jeons@gmail.com> wrote:
> Hi Andrew,
>
> On 04/05/2013 11:02 PM, Andrew Shewmaker wrote:
>>
>> On Wed, Apr 3, 2013 at 9:50 PM, Simon Jeons <simon.jeons@gmail.com> wrote:
>>>>
>>>> FAQ
>>>>
>> ...
>>>>
>>>>    * How do you calculate a minimum useful reserve?
>>>>
>>>>      A user or the admin needs enough memory to login and perform
>>>>      recovery operations, which includes, at a minimum:
>>>>
>>>>      sshd or login + bash (or some other shell) + top (or ps, kill,
>>>> etc.)
>>>>
>>>>      For overcommit 'guess', we can sum resident set sizes (RSS).
>>>>      On x86_64 this is about 8MB.
>>>>
>>>>      For overcommit 'never', we can take the max of their virtual sizes
>>>> (VSZ)
>>>>      and add the sum of their RSS.
>>>>      On x86_64 this is about 128MB.
>>>
>>>
>>> 1.Why has this different between guess and never?
>>
>> The default, overcommit 'guess' mode, only needs a reserve for
>> what the recovery programs will typically use. Overcommit 'never'
>> mode will only successfully launch an app when it can fulfill all of
>> its requested memory allocations--even if the app only uses a
>> fraction of what it asks for.
>
>
> VSZ has already cover RSS, is it? why account RSS again?

Right. Technically, I could leave out the RSS of the process that
I'm taking the VSZ of. Leaving it in makes the estimate 2-4 MB
larger, but it is just an estimate.

Choosing a good minimum is difficult because the behavior with
and without swap is different. With swap, only about 8MB reserves
are needed whether overcommit is disabled or not. Without swap,
I was always able to recover when I set the reserves to over 230MB
each. However, I was often able to recover with much less.

128MB seemed to me like a decent compromise between swap
and noswap modes, but it isn't totally safe for the case when
both swap and memory overcommit are disabled. In that case,
I think that an admin will have to tune the reserves for their specific
situation.

--
Andrew Shewmaker

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2013-04-08 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 13:42 Andrew Shewmaker
2013-04-04  3:50 ` Simon Jeons
2013-04-05 15:02   ` Andrew Shewmaker
2013-04-07  0:48     ` Simon Jeons
2013-04-08 18:49       ` Andrew Shewmaker [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=CAF-E8XHnTTUPm1s5RF2wEC-sjt3wYDhLgj__UQRz-b6AyC++vQ@mail.gmail.com \
    --to=agshew@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ric.masonn@gmail.com \
    --cc=simon.jeons@gmail.com \
    /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