From: Andrew Morton <akpm@osdl.org>
To: Jan Kasprzak <kas@informatics.muni.cz>
Cc: nathans@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Fw: Performance drop 2.6.0-test7 -> 2.6.1-rc2
Date: Thu, 8 Jan 2004 02:16:37 -0800 [thread overview]
Message-ID: <20040108021637.15d1b33a.akpm@osdl.org> (raw)
In-Reply-To: <20040108105427.E20265@fi.muni.cz>
Jan Kasprzak <kas@informatics.muni.cz> wrote:
>
> 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.
Is the CPU load higher than normal? Excluding I/O wait? If so, can you
profile the kernel while the load is running?
- boot with `profile=1' on the kernel command line
- establish steady state load
- Run readprofile -r
- sleep 120
- readprofile -n -v -m System.map | sort -n +2 | tail -40
(More info in Documentation/basic_profiling.txt)
Thanks.
x
next prev parent reply other threads:[~2004-01-08 10:17 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
2004-01-08 10:16 ` Andrew Morton [this message]
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=20040108021637.15d1b33a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=kas@informatics.muni.cz \
--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