From: Jan Kasprzak <kas@informatics.muni.cz>
To: Nathan Scott <nathans@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Fw: Performance drop 2.6.0-test7 -> 2.6.1-rc2
Date: Thu, 8 Jan 2004 10:54:27 +0100 [thread overview]
Message-ID: <20040108105427.E20265@fi.muni.cz> (raw)
In-Reply-To: <20040107215240.GA768@frodo>; from nathans@sgi.com on Thu, Jan 08, 2004 at 08:52:40AM +1100
Nathan Scott wrote:
: On Wed, Jan 07, 2004 at 02:30:42AM -0800, Andrew Morton wrote:
: >
: > Nathan, did anything change in XFS which might explain this?
:
: Just been back through the revision history, and thats a definate
: "no" - very little changed in 2.6 XFS while the big 2.6 freeze was
: on, and since then too (he says, busily preparing a merge tree).
:
: > I see XFS has some private readahead code. Anything change there?
:
: No, and that readahead code is used for metadata only - for file data
: we're making use of the generic IO path code.
:
I have done further testing:
- this is reliable: repeated boot back to 2.6.1-rc2 makes the problem
appear again (high load, system slow has hell), booting back
to -test7 makes it disappear.
- this is probably not a compiler/toolchain issue (tried to compile the kernel
using two different versions of gcc and system environment (RedHat 9
one and the latest Gentoo).
- I have seen something similar on my fileserver (altough I was not able
to research it thoroughly, because I had to went back to 2.4).
The fileserver is dual Athlon MP, 1GB RAM, 2TB of storage on
RAID-5 array on the 3ware controller. Most of its load is serving
home directories via NFS (cca 2200 users), and few Windows clients
via Samba 3.0.1. Filesystem is XFS as well, but I dont know whether
this can be a problem. I have tried 2.6.0 only, not earlier or
later revisions. 2.4.24-pre (XFS) works OK here.
If I can guess, I think it would be a problem with block layer
or I/O request scheduling rather than XFS.
-Yenya
--
| Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/ Czech Linux Homepage: http://www.linux.cz/ |
| I actually have a lot of admiration and respect for the PATA knowledge |
| embedded in drivers/ide. But I would never call it pretty:) -Jeff Garzik |
next prev parent reply other threads:[~2004-01-08 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040107023042.710ebff3.akpm@osdl.org>
2004-01-07 21:52 ` Nathan Scott
2004-01-08 9:54 ` Jan Kasprzak [this message]
2004-01-08 10:16 ` Andrew Morton
2004-01-08 10:25 ` Jan Kasprzak
2004-01-08 10:33 ` Andrew Morton
2004-01-08 11:01 ` Jan Kasprzak
2004-01-08 14:20 ` J. Ryan Earl
2004-01-08 12:07 ` Christoph Hellwig
2004-01-08 15:03 ` Jan Kasprzak
2004-01-08 15:11 ` Jan Kasprzak
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=20040108105427.E20265@fi.muni.cz \
--to=kas@informatics.muni.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
/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
Powered by JetHome