From: Hugh Dickins <hugh@veritas.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: overcommit stuff
Date: Sun, 22 Sep 2002 00:46:59 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0209220037110.2265-100000@localhost.localdomain> (raw)
In-Reply-To: <3D8D0046.EF119E03@digeo.com>
On Sat, 21 Sep 2002, Andrew Morton wrote:
> Alan,
>
> running 10,000 tiobench threads I'm showing 23 gigs of
> `Commited_AS'. Is this right? Those pages are shared,
> and if they're not PROT_WRITEable then there's no way in
> which they can become unshared? Seems to be excessively
> pessimistic?
>
> Or is 2.5 not up to date?
I don't think Alan can be held responsible for errors in the
overcommit stuff rml ported to 2.5 and I then added fixes to.
I believe it is up to date in 2.5.
Committed_AS certainly errs on the pessimistic side, that's
what it's about. How much swap do you have i.e. is 23GB
committed impossible, or just surprising to you? Does the
number go back to what it started off from when you kill
off the tests? How are "those pages" allocated e.g. what
mmap args?
Hugh
--
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-21 23:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-21 23:27 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 [this message]
2002-09-21 23:53 ` Andrew Morton
2002-09-22 0:49 ` Hugh Dickins
2002-09-22 1:07 ` Andrew Morton
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=Pine.LNX.4.44.0209220037110.2265-100000@localhost.localdomain \
--to=hugh@veritas.com \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox