mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: m.knoblauch@TeraPort.de, Martin.Bligh@us.ibm.com
Cc: "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 07:03:50 -0800	[thread overview]
Message-ID: <311985531.1014793429@[10.10.2.3]> (raw)
In-Reply-To: <3C7CB28A.CAD095B5@TeraPort.de>
In-Reply-To: <3C7CB28A.CAD095B5@TeraPort.de>

>> 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?

I think the last tests I was doing was on a 12cpu box, which
gave me about a 40% performance degredation by installing rmap.
Most people won't be interested in anything near that large,
but as Rik said, the problems will start on much smaller systems.
One of the nice things about running really large systems is
that they show up scalability problems and race conditions
really quickly and obviously ;-)

If someone has data for 4 or 8 way systems, I'd love to see it.
Else I'll get some myself in a little while.

Thanks,

Martin.


      parent reply	other threads:[~2002-02-27 15:32 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
2002-02-27 11:11     ` Rik van Riel
2002-02-27 15:03 ` Martin J. Bligh [this message]

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='311985531.1014793429@[10.10.2.3]' \
    --to=martin.bligh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.knoblauch@TeraPort.de \
    /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®