From: Tharindu Rukshan Bamunuarachchi <btharindu@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org, linux-nfs@vger.kernel.org
Subject: Re: TMPFS over NFSv4
Date: Mon, 24 May 2010 12:36:49 +0100 [thread overview]
Message-ID: <AANLkTilrt_DXeQcl2SKtRvYTt5DKDtV9DhUyZH3KzAZ8@mail.gmail.com> (raw)
In-Reply-To: <20100524110245.6b6d847d@lxorguk.ukuu.org.uk>
Got it cleared.
BTW, nice example ... US Banking System :-)
__
tharindu.info
"those that can, do. Those that can’t, complain." -- Linus
On Mon, May 24, 2010 at 11:02 AM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Mon, 24 May 2010 10:26:39 +0100
> Tharindu Rukshan Bamunuarachchi <btharindu@gmail.com> wrote:
>
>> thankx a lot Hugh ... I will try this out ... (bit harder patch
>> already patched SLES kernel :-p ) ....
>>
>> BTW, what does Alan means by "strict overcommit" ?
>
> Strict overcommit works like banks should. It tries to ensure that at any
> point it has sufficient swap and memory to fulfill any possible use of
> allocated address space. So in strict overcommit mode you should almost
> never see an OOM kill (there are perverse cases as always), but you will
> need a lot more swap that may well never be used.
>
> In the normal mode the kernel works like the US banking system and makes
> speculative guesses that all the resources it hands out will never be
> needed at once. That has the corresponding risk that one day it might at
> which point you get a meltdown (or in the kernel case OOM kills)
>
> Alan
>
--
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>
prev parent reply other threads:[~2010-05-24 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 13:47 Tharindu Rukshan Bamunuarachchi
2010-05-21 20:55 ` Hugh Dickins
2010-05-24 9:26 ` Tharindu Rukshan Bamunuarachchi
2010-05-24 9:57 ` Hugh Dickins
2010-05-24 10:09 ` Alan Cox
2010-05-24 23:46 ` Hugh Dickins
2010-05-25 9:00 ` Tharindu Rukshan Bamunuarachchi
2010-05-25 16:58 ` Greg KH
2010-05-25 17:00 ` Greg KH
2010-05-24 14:16 ` Tharindu Rukshan Bamunuarachchi
2010-05-24 10:02 ` Alan Cox
2010-05-24 11:36 ` Tharindu Rukshan Bamunuarachchi [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=AANLkTilrt_DXeQcl2SKtRvYTt5DKDtV9DhUyZH3KzAZ8@mail.gmail.com \
--to=btharindu@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.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