From: Daniel Phillips <phillips@bonn-fries.net>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
Shawn Starr <spstarr@sh0n.net>,
Linux <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19-preX: What we really need: -AA patches finally in the tree
Date: Sun, 24 Feb 2002 06:44:36 +0100 [thread overview]
Message-ID: <E16erSe-0001Qn-00@starship.berlin> (raw)
In-Reply-To: <200202260135.18913.Dieter.Nuetzel@hamburg.de> <1014686150.18834.2.camel@coredump> <4360000.1014687125@flay>
In-Reply-To: <4360000.1014687125@flay>
On February 26, 2002 02:32 am, Martin J. Bligh wrote:
> > Not to begin the flamewar, but no thanks. rmap-12f blows -aa away AFAIK
> > on this P200 w/ 64MB ram.
>
> rmap still sucks on large systems though.
But this is not a fundamental issue, it's implementation. Whereas non-rmap
will always suck on large systems, for fundamental reasons that are unrelated
to the quality of the implementation.
> I'd love to see rmap
> in the main kernel, but it needs to get the scalability fixed first.
Yes.
> The main problem seems to be pagemap_lru_lock ... Rik & crew
> know about this problem, but let's give them some time to fix it
> before rmap gets put into mainline ....
Yes, yes and yes.
--
Daniel
next prev parent reply other threads:[~2002-02-26 4:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 0:35 Dieter Nützel
2002-02-26 1:02 ` Ken Brownfield
2002-02-26 1:13 ` Andrew Morton
2002-02-26 7:20 ` Jens Axboe
2002-02-26 1:39 ` Alan Cox
2002-02-26 1:15 ` Shawn Starr
2002-02-26 8:36 ` Christoph Rohland
2002-02-26 1:32 ` Martin J. Bligh
2002-02-24 5:44 ` Daniel Phillips [this message]
2002-02-26 4:33 ` Martin J. Bligh
2002-02-26 11:42 ` Rik van Riel
2002-02-26 1:40 ` Rik van Riel
2002-02-26 1:49 ` Martin J. Bligh
2002-02-26 1:51 ` Alan Cox
2002-02-26 7:07 ` Christoph Hellwig
2002-02-26 16:21 ` Mike Fedyk
2002-02-26 16:53 ` Christoph Hellwig
2002-02-28 22:45 ` Bill Davidsen
2002-02-28 23:04 ` Rik van Riel
2002-03-01 1:04 ` 2.4.19-preX: What we really need: -AA patches finally in the Alan Cox
2002-03-01 1:14 ` Rik van Riel
2002-03-01 3:02 ` 2.4.19-preX: What we really need: -AA patches finally in the tree Bill Davidsen
2002-03-01 3:13 ` Rik van Riel
2002-03-01 3:43 ` Davide Libenzi
2002-03-01 10:36 ` Sean Hunter
2002-03-01 17:13 ` Davide Libenzi
2002-03-01 6:29 ` Olivier Galibert
2002-03-01 16:28 ` Dan Chen
2002-03-01 6:41 dart
2002-03-05 21:49 ` Bill Davidsen
2002-03-06 1:05 ` Alan Cox
2002-03-06 1:45 ` James M.
2002-03-06 16:50 ` Ken Brownfield
2002-03-07 10:11 ` Leonid Mamtchenkov
2002-03-06 23:34 ` Yven Leist
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=E16erSe-0001Qn-00@starship.berlin \
--to=phillips@bonn-fries.net \
--cc=Martin.Bligh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spstarr@sh0n.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®