From: Andrew Morton <akpm@digeo.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: overcommit stuff
Date: Sat, 21 Sep 2002 18:07:02 -0700 [thread overview]
Message-ID: <3D8D17B6.D4E1ECAE@digeo.com> (raw)
In-Reply-To: Pine.LNX.4.44.0209220129310.2339-100000@localhost.localdomain
Hugh Dickins wrote:
>
> ...
> > It seems very unlikely (impossible?) that those pages will
> > ever become unshared.
>
> I expect it's very unlikely (short of application bugs) that
> those pages would become unshared; but they have been mapped
> in such a way that the process is entitled to unshare them,
> therefore they have been counted. A good example of why
> Linux does not impose strict commit accounting, and why
> you may choose not to use Alan's strict accounting policy.
>
OK, thanks. Just checking.
Is glibc mapping executables with PROT_WRITE? If so,
doesn't that rather devalue the whole overcommit thing?
--
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/
next prev parent reply other threads:[~2002-09-22 1:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-21 23:27 overcommit stuff Andrew Morton
2002-09-21 23:28 ` William Lee Irwin III
2002-09-21 23:31 ` Martin J. Bligh
2002-09-22 0:03 ` Andrew Morton
2002-09-22 0:08 ` Martin J. Bligh
2002-09-22 1:04 ` Hugh Dickins
2002-09-22 1:07 ` Martin J. Bligh
2002-09-21 23:46 ` Hugh Dickins
2002-09-21 23:53 ` Andrew Morton
2002-09-22 0:49 ` Hugh Dickins
2002-09-22 1:07 ` Andrew Morton [this message]
2002-09-22 1:45 ` Hugh Dickins
2002-09-22 1:49 ` Andrew Morton
2002-09-21 23:53 ` William Lee Irwin III
2002-09-22 1:12 ` Andrew Morton
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=3D8D17B6.D4E1ECAE@digeo.com \
--to=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.