Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!ucbvax!bloom-beacon!mcgill-vision!mouse
From: mouse@mcgill-vision.UUCP (der Mouse)
Newsgroups: comp.unix.questions
Subject: Re: Meaning of csh "time" output?
Message-ID: <1055@mcgill-vision.UUCP>
Date: 16 Apr 88 07:29:13 GMT
References: <309@rhesus.primate.wisc.edu>
Organization: McGill University, Montreal
Lines: 43

In article <309@rhesus.primate.wisc.edu>, bin@rhesus.primate.wisc.edu (Brain in Neutral) writes:
> The csh "time" command produces lines of the form:
> 	0.1u 0.4s 0:01 41% 18+17k 0+11io 21pf+8w
> The csh manual explains the first 4 fields.  What do the rest mean?

From 4.2BSD csh source:

%Uu %Ss %E %P%% %X+%Dk %I+%Oio %Fpf+%Ww

%U	user time, seconds (ru_utime field of rusage struct)
%S	system time, seconds (ru_stime field of ditto)
%E	elapsed time, min:sec or hr:min:sec
%P	percentage of #:## accounted for by #.#u + #.#s
	 (ie, cpu utilization percentage)
%X	some sort of average (over time) of the text segment size
%D	ditto of the data+stack sizes
%I	"block input operations" (ru_inblock, see getrusage(2))
%O	"block output operations" (ru_oublock)
%F	page faults (from disk)
%W	swaps (entire process swapped)

%I and %O mean, according to the 4.3 man page for getrusage(), the
following:

ru_inblock	the number of times the file system had to perform
		input.

ru_outblock	the number of times the file system had to perform
     ^ [sic]	input.

Under NOTES, a warning appears:

The number ru_inblock and ru_outblock[sic] account only for real I/O;
data supplied by the caching mechanism is charged only to the first
process to read or write the data.

(grammar mistakes theirs).  And yes, <sys/resource.h> calls it
ru_oublock even though half the man page calls it ru_outblock.

					der Mouse

			uucp: mouse@mcgill-vision.uucp
			arpa: mouse@larry.mcrcim.mcgill.edu