From: hooanon05@yahoo.co.jp
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: __vm_enough_memory(), OVERCOMMIT_NEVER, current->mm, kernel thread
Date: Wed, 22 Oct 2008 14:35:16 +0900 [thread overview]
Message-ID: <6715.1224653716@jrobl> (raw)
In-Reply-To: <6775.1224630654@jrobl>
> I guess
> - people don't care overcommit and leave it as default, so they don't
> meet the problem
> - people who cares overcommit has rich memory, and they don't meet the
> problem too.
Correction: the problem is unrelated to the memory size.
I was sleepy when I wrote that.
Regardless the memory size, when nfsd writes to tmpfs the system surely
crashes.
Junjiro R. Okajima
next prev parent reply other threads:[~2008-10-22 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 15:14 __vm_enough_memory(), OVERCOMMIT_NEVER, current->mm, kernel thread hooanon05
2008-10-21 15:46 ` Alan Cox
2008-10-21 23:10 ` hooanon05
2008-10-22 5:35 ` hooanon05 [this message]
2008-10-22 8:27 ` Alan Cox
2008-10-22 11:26 ` hooanon05
2008-10-22 12:09 ` Alan Cox
2008-10-22 12:46 ` hooanon05
2008-10-22 13:37 ` James Morris
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=6715.1224653716@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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