From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Daniel Phillips <phillips@bonn-fries.net>,
Rob Fuller <rfuller@nsisoftware.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: broken VM in 2.4.10-pre9
Date: Wed, 19 Sep 2001 23:04:10 +0100 (BST) [thread overview]
Message-ID: <E15jpRy-0003yt-00@the-village.bc.nu> (raw)
In-Reply-To: <m1iteegag6.fsf@frodo.biederman.org> from "Eric W. Biederman" at Sep 19, 2001 03:03:21 PM
> That added to the fact that last time someone ran the numbers linux
> was considerably faster than the BSD for mm type operations when not
> swapping. And this is the common case.
"Linux VM works wonderfully when nobody is using it"
Which is rather like the scheduler works well for one task then by three is
making bad decisions.
> But I have not seen the argument that not having reverse maps make it
> undoable. In fact previous versions of linux seem to put the proof
> that you can get at least reasonable swapping under load without
> reverse page tables.
The last decent Linx VM behaviour was about 2.1.100 or so - which was
without reverse maps. It's been downhill since then. So yes you may be
right.
> So my suggestion was to look at getting anonymous pages backed by what
> amounts to a shared memory segment. In that vein. By using an extent
> based data structure we can get the cost down under the current 8 bits
> per page that we have for the swap counts, and make allocating swap
> pages faster. And we want to cluster related swap pages anyway so
> an extent based system is a natural fit.
Much of this goes away if you get rid of both the swap and anonymous page
special cases. Back anonymous pages with the "whoops everything I write here
vanishes mysteriously" file system and swap with a swapfs
Reverse mappings make linear aging easier to do but are not critical (we
can walk all physical pages via the page map array).
Alan
--
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:[~2001-09-19 22:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 15:40 Rob Fuller
2001-09-17 16:03 ` Eric W. Biederman
2001-09-19 9:45 ` Daniel Phillips
2001-09-19 19:45 ` Alan Cox
2001-09-19 21:03 ` Eric W. Biederman
2001-09-19 22:04 ` Alan Cox [this message]
2001-09-19 22:26 ` Eric W. Biederman
2001-09-19 23:05 ` Rik van Riel
2001-09-20 11:28 ` Daniel Phillips
2001-09-20 12:06 ` Rik van Riel
2001-09-21 8:13 ` Daniel Phillips
2001-09-21 12:10 ` Rik van Riel
2001-09-21 15:27 ` Jan Harkes
2001-09-22 7:09 ` Daniel Phillips
2001-09-25 11:04 ` Mike Fedyk
2001-09-20 12:57 ` Alan Cox
2001-09-20 13:40 ` Daniel Phillips
2001-09-24 22:50 ` Pavel Machek
2001-09-26 18:22 ` Marcelo Tosatti
2001-09-26 23:44 ` Pavel Machek
2001-09-27 13:52 ` Eric W. Biederman
2001-10-01 11:37 ` Marcelo Tosatti
2001-09-19 23:00 ` Rik van Riel
2001-09-21 8:23 ` Eric W. Biederman
2001-09-21 12:01 ` Rik van Riel
2001-09-22 2:14 ` Alexander Viro
2001-09-22 3:09 ` Rik van Riel
2001-09-19 21:37 ` Eric W. Biederman
2001-09-19 21:55 ` David S. Miller
2001-09-20 13:02 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2001-09-19 22:15 Rob Fuller
2001-09-19 22:21 ` David S. Miller
2001-09-19 22:30 ` Alan Cox
2001-09-19 22:48 ` Eric W. Biederman
2001-09-19 22:51 ` Bryan O'Sullivan
[not found] <Pine.LNX.4.33L.0109161330000.9536-100000@imladris.rielhome.conectiva>
2001-09-17 8:06 ` Eric W. Biederman
2001-09-17 12:12 ` Rik van Riel
2001-09-17 15:45 ` Eric W. Biederman
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=E15jpRy-0003yt-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=phillips@bonn-fries.net \
--cc=rfuller@nsisoftware.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