From: Nick Piggin <piggin@cyberone.com.au>
To: Samium Gromoff <deepfire@sic-elvis.zel.ru>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, philip@codematters.co.uk
Subject: Re: 2.6.1 slower than 2.4, smp/scsi/sw-raid/reiserfs
Date: Tue, 03 Feb 2004 18:57:27 +1100 [thread overview]
Message-ID: <401F5467.50702@cyberone.com.au> (raw)
In-Reply-To: <87r7xcy4zy.wl@canopus.ns.zel.ru>
Samium Gromoff wrote:
>At Mon, 2 Feb 2004 23:07:45 -0800,
>Andrew Morton wrote:
>
>
>>Samium Gromoff <deepfire@sic-elvis.zel.ru> wrote:
>>
>>
>>>
>>>
>>>>>The machine is a dual P3 450MHz, 512MB, aic7xxx, 2 disk RAID-0 and
>>>>> ReiserFS. It's a few years old and has always run Linux, most
>>>>> recently 2.4.24. I decided to try 2.6.1 and the performance is
>>>>> disappointing.
>>>>>
>>>>>
>>>>
>>>>2.6 has a few performance problems under heavy pageout at present. Nick
>>>>Piggin has some patches which largely fix it up.
>>>>
>>>>
>>>I`m sorry, but this is misguiding. 2.6 does not have a few performance
>>>problems under heavy pageout.
>>>
>>>
>>>
>>As you have frequently and somewhat redundantly reminded us.
>>
>>
>
>Right. I`m rather emotional about this...
>
>Kind of hard seeing the all starry and shiny 2.6 going down the toilet on my
>little server with 16M RAM.
>
>
>
>>Perhaps you could test Nick's patches. They are at
>>
>> http://www.kerneltrap.org/~npiggin/vm/
>>
>>Against 2.6.2-rc2-mm2. First revert vm-rss-limit-enforcement.patch, then
>>apply those three.
>>
>>
>
>Hmmm, i`d prefer plain 2.6, but i`ll try it anyway.
>
>
>
It should go against plain 2.6 with luck.
next prev parent reply other threads:[~2004-02-03 7:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 6:55 2.6.1 slower than 2.4, smp/scsi/sw-raid/reiserfs Samium Gromoff
2004-02-03 7:07 ` Andrew Morton
2004-02-03 7:52 ` Samium Gromoff
2004-02-03 7:57 ` Nick Piggin [this message]
2004-02-03 15:58 ` Valdis.Kletnieks
2004-02-03 7:13 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2004-02-01 21:34 Philip Martin
2004-02-01 23:11 ` Andrew Morton
2004-02-01 23:42 ` Philip Martin
2004-02-01 23:52 ` Nick Piggin
2004-02-02 0:51 ` Philip Martin
2004-02-02 5:15 ` Nick Piggin
2004-02-02 8:58 ` Nick Piggin
2004-02-02 18:36 ` Philip Martin
2004-02-02 23:36 ` Nick Piggin
2004-02-02 23:49 ` Andrew Morton
2004-02-03 1:01 ` Philip Martin
2004-02-03 3:02 ` Nick Piggin
2004-02-03 16:44 ` Philip Martin
2004-02-03 0:34 ` Philip Martin
2004-02-03 3:52 ` Nick Piggin
2004-02-02 18:08 ` Philip Martin
2004-02-03 3:46 ` Andrew Morton
2004-02-03 16:46 ` Philip Martin
2004-02-03 21:29 ` Andrew Morton
2004-02-03 21:53 ` Philip Martin
2004-02-04 5:48 ` Nick Piggin
2004-02-04 17:50 ` Philip Martin
2004-02-04 23:38 ` Philip Martin
2004-02-05 2:49 ` Nick Piggin
2004-02-05 14:27 ` Philip Martin
2004-02-14 0:10 ` Philip Martin
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=401F5467.50702@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=deepfire@sic-elvis.zel.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=philip@codematters.co.uk \
/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