From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nicholas Miell <nmiell@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: overcommit verses MAP_NORESERVE
Date: Mon, 08 Aug 2005 11:41:01 +0100 [thread overview]
Message-ID: <1123497662.28681.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1123485777.17857.10.camel@localhost.localdomain>
On Llu, 2005-08-08 at 00:22 -0700, Nicholas Miell wrote:
> I don't think you can forcibly reclaim MAP_NORESERVE objects (I'm
> assuming you mean completely throwing away dirty pages).
In which case there is no real difference between MAP_NORESERVE and not
setting it when doing zero overcommit as we do the accounting currently.
> not other errors) and individual writes to unallocated pages in a
> MAP_NORESERVE region should either allocate a new page if possible or
> send a SIGSEGV without triggering the OOM killer.
You'd need to track vma cost seperately which we don't do now and adjust
it for such mappings in the page faulting cases. Certainly practical -
send a patch
prev parent reply other threads:[~2005-08-08 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 3:52 overcommit verses MAP_NORESERVE Nicholas Miell
2005-08-07 11:49 ` Alan Cox
2005-08-08 7:22 ` Nicholas Miell
2005-08-08 10:41 ` Alan Cox [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=1123497662.28681.2.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nmiell@comcast.net \
/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