From: "Scott L. Burson" <gyro@zeta-soft.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Mathieu.Malaterre@creatis.insa-lyon.fr
Subject: Re: SMP performance problem in 2.4 (was: Athlon spinlock performance)
Date: Sun, 3 Aug 2003 03:00:02 -0700 (PDT) [thread overview]
Message-ID: <16172.14411.843546.121234@kali.zeta-soft.com> (raw)
In-Reply-To: <20030802144422.111d6893.akpm@osdl.org>
From: Andrew Morton <akpm@osdl.org>
Date: Sat, 2 Aug 2003 14:44:22 -0700
It is a problem which has been solved for a year at least. Try
running one of Andrea's kernels, from
ftp://ftp.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4
The most important patch for you is 10_inode-highmem-2.
I tried that patch by itself and it appeared to make a noticeable
improvement, but it was far from a complete fix.
So next I tried the SuSE 8.2 kernel. It is clearly *much* better, and I see
that Andrea in fact did a bit of work on `mm/vmscan.c'. The key patch
appears to be `05_vm_06_swap_out-3', but it's possible that several or all
of the `05_vm_*' patches are helpful.
I see that even the very most recent Red Hat kernel (2.4.20-19.7, released
only two weeks ago) does not seem to have these fixes. (I wasn't running Red
Hat -- my machine started out with SuSE 7.3, and I hand-upgraded it to
2.4.18 -- but Mathieu Malaterre, who is CCed above and whose query to me
about the problem got me started looking at it again, is using Red Hat.)
So I strongly urge the powers that be to include these patches in 2.4.22.
-- Scott
next prev parent reply other threads:[~2003-08-03 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 20:03 SMP performance problem in 2.4 (was: Athlon spinlock performance) Scott L. Burson
2003-08-02 21:44 ` Andrew Morton
2003-08-03 10:00 ` Scott L. Burson [this message]
2003-08-06 2:37 ` Rik van Riel
2003-08-03 2:40 ` Rik van Riel
2003-08-03 5:18 ` Con Kolivas
2003-08-06 17:21 Manfred Spraul
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=16172.14411.843546.121234@kali.zeta-soft.com \
--to=gyro@zeta-soft.com \
--cc=Mathieu.Malaterre@creatis.insa-lyon.fr \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).