From owner-freebsd-hackers Tue Nov 7 7:13:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 85BC437B479 for ; Tue, 7 Nov 2000 07:13:37 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id QAA49454; Tue, 7 Nov 2000 16:13:31 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: void Cc: hackers@FreeBSD.ORG Subject: Re: "iowait" CPU state References: <20001107054413.A1983@firedrake.org> From: Dag-Erling Smorgrav Date: 07 Nov 2000 16:13:30 +0100 In-Reply-To: void's message of "Tue, 7 Nov 2000 05:44:13 +0000" Message-ID: Lines: 14 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG void writes: > I've been using Solaris a lot lately, and I've noticed that in e.g. > top's output, it has a distinct CPU state called "iowait", which seems > to be a pretty good indicator of how I/O-bound a system is. Is there > any reason that FreeBSD doesn't have such a state? It has several, depending on the type of I/O the process is waiting for: biord (waiting for a read operation to complete), biowr (waiting for a write operation to complete), select (waiting for descriptors to become readable / writable), etc. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message