Re: High load average on disk I/O on 2.6.17-rc3
- From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
- Date: Mon, 08 May 2006 16:55:48 +0200
On Mon, 2006-05-08 at 07:24 -0700, Martin J. Bligh wrote:
It's pretty harmless though. The "load average" thing just means that the
extra pdflush threads are twiddling thumbs waiting on some disk I/O -
they'll later exit and clean themselves up. They won't be consuming
significant resources.
If they're waiting on disk I/O, they shouldn't be runnable, and thus
should not be counted as part of the load average, surely?
yes they are, since at least a decade. "load average" != "cpu
utilisation" by any means. It's "tasks waiting for a hardware resource
to become available". CPU is one such resource (runnable) but disk is
another. There are more ...
think of load as "if I bought faster hardware this would improve"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: High load average on disk I/O on 2.6.17-rc3
- From: Erik Mouw
- Re: High load average on disk I/O on 2.6.17-rc3
- References:
- High load average on disk I/O on 2.6.17-rc3
- From: Jason Schoonover
- Re: High load average on disk I/O on 2.6.17-rc3
- From: Andrew Morton
- Re: High load average on disk I/O on 2.6.17-rc3
- From: Martin J. Bligh
- High load average on disk I/O on 2.6.17-rc3
- Prev by Date: Re: How to read BIOS information
- Next by Date: Re: [PATCH] make kernel ignore bogus partitions
- Previous by thread: Re: High load average on disk I/O on 2.6.17-rc3
- Next by thread: Re: High load average on disk I/O on 2.6.17-rc3
- Index(es):
Relevant Pages
|