| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <465C5B61.6000702@redhat.com> Date: Tue, 29 May 2007 12:57:05 -0400 From: Rik van Riel <riel@...hat.com> To: Bill Davidsen <davidsen@....com> CC: Linux Kernel mailing List <linux-kernel@...r.kernel.org> Subject: Re: What causes iowait other than waiting for i/o? Bill Davidsen wrote: > 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. All filesystem IO and direct disk IO can cause iowait. This includes NFS activity. -- Politics is the struggle between those who want to make their country the best in the world, and those who believe it already is. Each group calls the other unpatriotic. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists