From: Robert Hancock <hancockr@shaw.ca>
To: Jason Schoonover <jasons@pioneer-pra.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: High load average on disk I/O on 2.6.17-rc3
Date: Sat, 06 May 2006 11:20:16 -0600 [thread overview]
Message-ID: <445CDAD0.1000203@shaw.ca> (raw)
In-Reply-To: <200605052139.49241.jasons@pioneer-pra.com>
Jason Schoonover wrote:
> Hi Robert,
>
> There are, this is the relevant output of the process list:
>
> ...
> 4659 pts/6 Ss 0:00 -bash
> 4671 pts/5 R+ 0:12 cp -a test-dir/ new-test
> 4676 ? D 0:00 [pdflush]
> 4679 ? D 0:00 [pdflush]
> 4687 pts/4 D+ 0:01 hdparm -t /dev/sda
> 4688 ? D 0:00 [pdflush]
> 4690 ? D 0:00 [pdflush]
> 4692 ? D 0:00 [pdflush]
> ...
>
> This was when I was copying a directory and then doing a performance test with
> hdparm in a separate shell. The hdparm process was in [D+] state and
> basically waited until the cp was finished. During the whole thing there
> were up to 5 pdflush processes in [D] state.
>
> The 5 minute load average hit 8.90 during this test.
>
> Does that help?
Well, it obviously explains why the load average is high, those D state
processes all count in the load average. It may be sort of a cosmetic
issue, since they're not actually using any CPU, but it's still a bit
unusual. For one thing, not sure why there are that many of them?
You could try enabling the SysRq triggers (if they're not already in
your kernel/distro) and doing Alt-SysRq-T which will dump the kernel
stack of all processes, that should show where exactly in the kernel
those pdflush processes are blocked..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next prev parent reply other threads:[~2006-05-06 17:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <69c8K-3Bu-57@gated-at.bofh.it>
2006-05-05 23:12 ` High load average on disk I/O on 2.6.17-rc3 Robert Hancock
2006-05-06 4:39 ` Jason Schoonover
2006-05-06 17:20 ` Robert Hancock [this message]
2006-05-06 18:23 ` Jason Schoonover
2006-05-06 20:01 ` Robert Hancock
2006-05-05 17:10 Jason Schoonover
2006-05-06 23:03 ` bert hubert
2006-05-07 1:02 ` Jason Schoonover
2006-05-07 10:54 ` bert hubert
2006-05-07 16:50 ` Andrew Morton
2006-05-07 17:24 ` Jason Schoonover
2006-05-08 11:13 ` Erik Mouw
2006-05-08 11:22 ` Arjan van de Ven
2006-05-08 11:28 ` Russell King
2006-05-08 11:38 ` Avi Kivity
2006-05-08 12:37 ` Arjan van de Ven
2006-05-09 14:37 ` Bill Davidsen
2006-05-08 14:24 ` Martin J. Bligh
2006-05-08 14:55 ` Arjan van de Ven
2006-05-08 15:22 ` Erik Mouw
2006-05-08 15:25 ` Martin J. Bligh
2006-05-08 15:31 ` Arjan van de Ven
2006-05-08 15:42 ` Erik Mouw
2006-05-08 16:02 ` Martin J. Bligh
2006-05-08 16:02 ` Miquel van Smoorenburg
2006-05-08 16:47 ` Russell King
2006-05-08 17:04 ` Gabor Gombas
2006-05-08 17:18 ` Mike Galbraith
2006-05-09 1:57 ` Nick Piggin
2006-05-09 2:02 ` Martin Bligh
2006-05-09 2:16 ` Nick Piggin
2006-05-09 4:36 ` Arjan van de Ven
2006-05-09 4:46 ` Nick Piggin
2006-05-09 5:27 ` Hua Zhong
2006-05-09 5:03 ` David Lang
2006-05-15 7:46 ` Sander
2006-05-08 22:24 ` Bernd Eckenfels
2006-05-08 22:39 ` Lee Revell
2006-05-09 0:08 ` Peter Williams
2006-05-09 18:33 ` Bill Davidsen
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=445CDAD0.1000203@shaw.ca \
--to=hancockr@shaw.ca \
--cc=jasons@pioneer-pra.com \
--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).