From: Linus Torvalds <torvalds@transmeta.com>
To: Alan Cox <alan@redhat.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
Hugh Dickins <hugh@veritas.com>, Ben LaHaise <bcrl@redhat.com>,
Rik van Riel <riel@conectiva.com.br>,
Richard Jerrrell <jerrell@missioncriticallinux.com>,
Stephen Tweedie <sct@redhat.com>,
arjanv@redhat.com, linux-mm@kvack.org
Subject: Re: [PATCH] swap_state.c thinko
Date: Mon, 9 Apr 2001 13:32:41 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.31.0104091316500.9383-100000@penguin.transmeta.com> (raw)
In-Reply-To: <200104091816.f39IGxD16018@devserv.devel.redhat.com>
On Mon, 9 Apr 2001, Alan Cox wrote:
>
> Given that strict address space management is not that hard would you
> accept patches to allow optional non-overcommit in 2.5
I really doubt anybody wants to use a truly non-overcommit system.
It would basically imply counting every single vma that is privately
writable, and assuming it becomes totally non-shared.
Try this on your system as root:
cat /proc/*/maps | grep ' .w.p '
and see how much memory that is.
On my machine, running X, that's about 53M with just a few windows open if
I did my script right. It grew to 159M when starting StarOffice.
(I'm oldfashioned, and not a perl person, so:
cat /proc/*/maps |
grep 'w.p ' |
cut -d' ' -f1 |
tr '-' ' ' |
while read i j; do export k=$(($k + 0x$j-0x$i)) ; echo $k; done
I haven't verified that it gets it right. And that's not counting the
really hardwired pages at all, only th epages that might be pageable).
It would disallow a lot of stuff that actually _does_ work in practice.
But maybe some people do want this. I agree that it shouldn't be
fundamentally hard to do accounting at the vma level.
Linus
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-04-09 20:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 15:56 Ben LaHaise
2001-04-05 16:05 ` Rik van Riel
2001-04-05 17:11 ` Ben LaHaise
2001-04-05 23:40 ` Andrea Arcangeli
2001-04-06 0:32 ` Linus Torvalds
2001-04-06 16:31 ` Hugh Dickins
2001-04-06 17:21 ` Linus Torvalds
2001-04-06 18:23 ` Hugh Dickins
2001-04-06 18:57 ` Linus Torvalds
2001-04-06 19:06 ` Rik van Riel
2001-04-06 18:47 ` Andrea Arcangeli
2001-04-06 18:37 ` Hugh Dickins
2001-04-06 19:09 ` Andrea Arcangeli
2001-04-06 18:53 ` Hugh Dickins
2001-04-06 19:14 ` Andrea Arcangeli
2001-04-06 19:03 ` Hugh Dickins
2001-04-06 20:03 ` Andrea Arcangeli
2001-04-06 19:12 ` Richard Jerrell
2001-04-06 19:52 ` Linus Torvalds
2001-04-06 20:22 ` Andrea Arcangeli
2001-04-06 21:04 ` Rik van Riel
2001-04-07 1:27 ` Andrea Arcangeli
2001-04-09 18:16 ` Alan Cox
2001-04-09 18:45 ` Andrea Arcangeli
2001-04-09 20:32 ` Linus Torvalds [this message]
2001-04-09 20:54 ` David L. Parsley
2001-04-10 21:07 ` James Antill
2001-04-10 22:20 ` Jeff Garzik
2001-04-06 20:48 ` Hugh Dickins
2001-04-05 17:21 ` Hugh Dickins
2001-04-05 21:39 ` Richard Jerrell
2001-04-06 20:20 Bulent Abali
2001-04-06 20:33 ` Jeff Garzik
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.31.0104091316500.9383-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=alan@redhat.com \
--cc=andrea@suse.de \
--cc=arjanv@redhat.com \
--cc=bcrl@redhat.com \
--cc=hugh@veritas.com \
--cc=jerrell@missioncriticallinux.com \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=sct@redhat.com \
/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