From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: What causes iowait other than waiting for i/o?
Date: Mon, 28 May 2007 17:36:53 -0400 [thread overview]
Message-ID: <465B4B75.2040602@tmr.com> (raw)
I recently noted that my system was spending a lot of time in i/o wait
when doing some tasks which I thought didn't involve i/o, as noted by
the lack of disk light activity most of the time. I thought of network,
certainly the NIC had no activity for this job. So I set up a little
loop to capture all disk i/o and network activity (including loopback).
That was no obvious help, and the program doesn't use pipes.
At this point I'm really curious, does someone have a good clue?
Note: I don't think this is a bug or performance issue, unless the
kernel is doing something and charging time to iowait instead of system
I don't see anything to fix, but I would like to understand.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next reply other threads:[~2007-05-28 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 21:36 Bill Davidsen [this message]
2007-05-28 21:47 ` What causes iowait other than waiting for i/o? Jesper Juhl
2007-05-29 6:28 ` Satyam Sharma
2007-05-29 13:26 ` Bill Davidsen
2007-05-29 16:57 ` Rik van Riel
2007-05-29 20:01 ` 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=465B4B75.2040602@tmr.com \
--to=davidsen@tmr.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