From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <acc29a142e185683e3abdf720e1e69e2@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] iostats ?
From: rog@vitanuova.com
In-Reply-To: <2253a24e2a11bf185122eca8a2f51531@yourdomain.dom>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Thu, 24 Jul 2003 15:25:14 +0100
Topicbox-Message-UUID: 024f5cc8-eacc-11e9-9e20-41e7f4b1d025

> 	iostats ls /bin /bin/* > /dev/null
> reports zero average time for all 9p operations, and
[...]
> and some impressive throughput rates...

it's been broken, quite recently it seems.
in /sys/src/cmd/iostats/statsrv.c:/^update change

<	ulong t2;
<
<	t2 = msec();
<	t -= t2;

to

>	t = msec() - t;

then the numbers become non-zero, at least.

the e+07 numbers are due to the dodgy "avoid zero devide" hack
in iostats.c:

	brpsec = (float)stats->totread / (((float)rpc->time/1000.0)+.000001);
	bwpsec = (float)stats->totwrite / (((float)rpc->time/1000.0)+.000001);
	bppsec = (float)stats->nproto / ((ttime/1000.0)+.000001);

maybe it'd be less misleading just to do:

	setfcr(getfcr() & ~FPZDIV);

before the calculations, and remove the .000001 fudge factor: then if
there were no ops the throughput comes out as +Inf.