From: Martin Knoblauch <Martin.Knoblauch@TeraPort.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Martin.Bligh@us.ibm.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19-preX: What we really need: -AA patches finally in thetree
Date: Wed, 27 Feb 2002 12:06:40 +0100 [thread overview]
Message-ID: <3C7CBDC0.9F9CDBAC@TeraPort.de> (raw)
In-Reply-To: <Pine.LNX.4.33L.0202270800420.7820-100000@imladris.surriel.com>
Rik van Riel wrote:
>
> On Wed, 27 Feb 2002, Martin Knoblauch 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. I'd love to see rmap
> > > in the main kernel, but it needs to get the scalability fixed first.
> > > 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 ....
> >
> > just out of curiosity: where does "large systems" start in your
> > context?
>
> My guess it would start at about 4 or 8 CPUs.
>
> Systems which have a lot of pagetable overhead would also
> suffer with -rmap, until -rmap supports pte_highmem.
>
So, what about a Dual-Athlon system with 2-3 GB of memory? Large
system, or just a peanut? :-)
Martin
--
------------------------------------------------------------------
Martin Knoblauch | email: Martin.Knoblauch@TeraPort.de
TeraPort GmbH | Phone: +49-89-510857-309
C+ITS | Fax: +49-89-510857-111
http://www.teraport.de | Mobile: +49-170-4904759
next prev parent reply other threads:[~2002-02-27 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 10:18 Martin Knoblauch
2002-02-27 11:01 ` Rik van Riel
2002-02-27 11:06 ` Martin Knoblauch [this message]
2002-02-27 11:11 ` Rik van Riel
2002-02-27 15:03 ` Martin J. Bligh
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=3C7CBDC0.9F9CDBAC@TeraPort.de \
--to=martin.knoblauch@teraport.de \
--cc=Martin.Bligh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.knoblauch@TeraPort.de \
--cc=riel@conectiva.com.br \
/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®