From: Nick Piggin <piggin@cyberone.com.au>
To: Philip Martin <philip@codematters.co.uk>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.1 slower than 2.4, smp/scsi/sw-raid/reiserfs
Date: Wed, 04 Feb 2004 16:48:35 +1100 [thread overview]
Message-ID: <402087B3.1080302@cyberone.com.au> (raw)
In-Reply-To: <87znbzg78o.fsf@codematters.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
Philip Martin wrote:
>Andrew Morton <akpm@osdl.org> writes:
>
>
>>>2.6.1
>>>
>>Odd. Are you really sure that it was the correct System.map?
>>
>
>I think so. I always build kernels using Debian's kernel-package so
>both vmlinuz and System.map get placed into a .deb package as
>vmlinuz-2.6.1 and System.map-2.6.1.
>
>$ ls -l /boot/Sys*
>-rw-r--r-- 1 root root 492205 Dec 1 19:27 /boot/System.map-2.4.23
>-rw-r--r-- 1 root root 492205 Jan 5 21:21 /boot/System.map-2.4.24
>-rw-r--r-- 1 root root 715800 Feb 1 21:02 /boot/System.map-2.6.1
>
>$ ls -l /boot/vm*
>-rw-r--r-- 1 root root 880826 Dec 1 19:27 /boot/vmlinuz-2.4.23
>-rw-r--r-- 1 root root 880822 Jan 5 21:21 /boot/vmlinuz-2.4.24
>-rw-r--r-- 1 root root 1095040 Feb 1 21:02 /boot/vmlinuz-2.6.1
>
>Hmm, I see that my 2.6.1 image is 25% bigger than 2.4.24, I'd not
>noticed that before.
>
>
That's progress for you...
>I have just tried another 2.6 profile run and got similar results.
>
>248.88user 122.00system 3:41.18elapsed 167%CPU (0avgtext+0avgdata 0maxresident)k
>0inputs+0outputs (453major+3770323minor)pagefaults 0swaps
>
>
Thanks for your patience. What are you building, by the way? It
slipped my mind.
You could try an experimental VM patch out if you're feeling brave.
Don't know if it will do you any good or not. You'll have to use
this patch against the 2.6.2-rc3-mm1 kernel.
What I really want to know though, is why it appears like 2.6 is
doing twice as much writeout even at the same vm thresholds as 2.4.
Nick
[-- Attachment #2: vm-swap-3.gz --]
[-- Type: application/x-tar, Size: 7298 bytes --]
next prev parent reply other threads:[~2004-02-04 5:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 21:34 2.6.1 slower than 2.4, smp/scsi/sw-raid/reiserfs 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 6:55 Samium Gromoff
2004-02-03 7:07 ` Andrew Morton
2004-02-03 7:52 ` Samium Gromoff
2004-02-03 7:57 ` Nick Piggin
2004-02-03 15:58 ` Valdis.Kletnieks
2004-02-03 7:13 ` Nick Piggin
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=402087B3.1080302@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--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