mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Hugh Dickins <hugh@veritas.com>
Cc: Robert Love <rml@tech9.net>, David Mosberger <davidm@hpl.hp.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VM accounting 1/3 trivial
Date: 25 Jul 2002 02:31:54 +0100	[thread overview]
Message-ID: <1027560714.6456.43.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0207241453420.1159-100000@localhost.localdomain>

On Wed, 2002-07-24 at 15:48, Hugh Dickins wrote:
> Thank you, it is surely incorrect (in the case where the do_munmap does
> not cover the whole vma, leaving one or two pieces behind: I think that
> must be the case you're remembering).  Would a patch which (if necessary)
> reapplies VM_ACCOUNT to the leftover piece(s) be welcome, or would it
> just look like an ugly face-saving exercise?

I went around this about five times before changing do_munmap having
failed dismally on each case. I wouldnt worry about face saving, I made
the same mistake and spent a couple of days debugging it.

> But I'll still have a consistency problem with MAP_NORESERVE versus
> sysctl_overcommit_memory, when the latter is changed (> 1 or <= 1).

Its very simple. If you have said "no overcommit" you cannot allow
anyone to violate the rule because any reservation could cause someone
who didnt NORESERVE to get killed off.

Secondly on my test runs, no process on a standard distro seems to use
NORESERVE anyway 8)


  reply	other threads:[~2002-07-25  0:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-23 17:27 Hugh Dickins
2002-07-23 17:28 ` [PATCH] VM accounting 2/3 fixes Hugh Dickins
2002-07-23 17:29 ` [PATCH] VM accounting 3/3 noreserve Hugh Dickins
2002-07-23 17:36   ` David Mosberger
2002-07-23 22:33 ` [PATCH] VM accounting 1/3 trivial Alan Cox
2002-07-24 14:48   ` Hugh Dickins
2002-07-25  1:31     ` Alan Cox [this message]
2002-07-25 20:31       ` Hugh Dickins
2002-07-25 22:31         ` Alan Cox

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=1027560714.6456.43.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=davidm@hpl.hp.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.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

all inboxes | Powered by JetHome®