vtimes(3) [ultrix man page]

vtimes(3)						     Library Functions Manual							 vtimes(3)

Name
       vtimes - get information about resource utilization

Syntax
       vtimes(par_vm, ch_vm)
       struct vtimes *par_vm, *ch_vm;

Description
       This facility has been superseded by

       The  routine  returns accounting information for the current process and for the terminated child processes of the current process.  Either
       par_vm or ch_vm or both may be 0, in which case only the information for the pointers which are non-zero is returned.

       After the call, each buffer contains information as defined by the contents of the include file /usr/include/sys/vtimes.h:
       struct vtimes {
	    int     vm_utime;		    /* user time (*HZ) */
	    int  vm_stime;	/* system time (*HZ) */
	    /* divide next two by utime+stime to get averages */
	    unsigned vm_idsrss;      /* integral of d+s rss */
	    unsigned vm_ixrss;	     /* integral of text rss */
	    int  vm_maxrss;	     /* maximum rss */
	    int  vm_majflt;	     /* major page faults */
	    int  vm_minflt;	     /* minor page faults */
	    int  vm_nswap;	/* number of swaps */
	    int  vm_inblk;	/* block reads */
	    int  vm_oublk;	/* block writes */
       };
       The vm_utime and vm_stime fields give the user and system time respectively in 60ths of a second (or 50ths if that is the frequency of wall
       current	in your locality.) The vm_idrss and vm_ixrss measure memory usage.  They are computed by integrating the number of memory pages in
       use each over cpu time.	They are reported as though computed discretely, adding the current memory usage (in 512 byte pages) each time the
       clock  ticks.   If  a  process  used 5 core pages over 1 cpu-second for its data and stack, then vm_idsrss would have the value 5*60, where
       vm_utime+vm_stime would be the 60. The vm_idsrss integrates data and stack segment usage, while vm_ixrss  integrates  text  segment  usage.
       The vm_maxrss reports the maximum instantaneous sum of the text+data+stack core-resident page count.

       The  vm_majflt  field  gives the number of page faults which resulted in disk activity; the vm_minflt field gives the number of page faults
       incurred in simulation of reference bits; vm_nswap is the number of swaps which occurred.  The number of file  system  input/output  events
       are  reported  in vm_inblk and vm_oublk These numbers 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.

See Also
       wait3(2), time(3)

																	 vtimes(3)

GETRUSAGE(2)						      BSD System Calls Manual						      GETRUSAGE(2)

NAME

     getrusage -- get information about resource utilization

SYNOPSIS

     #include <sys/time.h>
     #include <sys/resource.h>
     #define   RUSAGE_SELF     0
     #define   RUSAGE_CHILDREN	   -1

     int
     getrusage(int who, struct rusage *rusage);

DESCRIPTION

     Getrusage() returns information describing the resources utilized by the current process, or all its terminated child processes.  The who
     parameter is either RUSAGE_SELF or RUSAGE_CHILDREN.  The buffer to which rusage points will be filled in with the following structure:

     struct rusage {
	     struct timeval ru_utime; /* user time used */
	     struct timeval ru_stime; /* system time used */
	     long ru_maxrss;	      /* integral max resident set size */
	     long ru_ixrss;	      /* integral shared text memory size */
	     long ru_idrss;	      /* integral unshared data size */
	     long ru_isrss;	      /* integral unshared stack size */
	     long ru_minflt;	      /* page reclaims */
	     long ru_majflt;	      /* page faults */
	     long ru_nswap;	      /* swaps */
	     long ru_inblock;	      /* block input operations */
	     long ru_oublock;	      /* block output operations */
	     long ru_msgsnd;	      /* messages sent */
	     long ru_msgrcv;	      /* messages received */
	     long ru_nsignals;	      /* signals received */
	     long ru_nvcsw;	      /* voluntary context switches */
	     long ru_nivcsw;	      /* involuntary context switches */
     };

     The fields are interpreted as follows:

     ru_utime	  the total amount of time spent executing in user mode.

     ru_stime	  the total amount of time spent in the system executing on behalf of the process(es).

     ru_maxrss	  the maximum resident set size utilized (in kilobytes).

     ru_ixrss	  an integral value indicating the amount of memory used by the text segment that was also shared among other processes.  This
		  value is expressed in units of kilobytes * ticks-of-execution.

     ru_idrss	  an integral value of the amount of unshared memory residing in the data segment of a process (expressed in units of kilobytes *
		  ticks-of-execution).

     ru_isrss	  an integral value of the amount of unshared memory residing in the stack segment of a process (expressed in units of kilobytes *
		  ticks-of-execution).

     ru_minflt	  the number of page faults serviced without any I/O activity; here I/O activity is avoided by reclaiming a page frame from the
		  list of pages awaiting reallocation.

     ru_majflt	  the number of page faults serviced that required I/O activity.

     ru_nswap	  the number of times a process was swapped out of main memory.

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

     ru_oublock   the number of times the file system had to perform output.

     ru_msgsnd	  the number of IPC messages sent.

     ru_msgrcv	  the number of IPC messages received.

     ru_nsignals  the number of signals delivered.

     ru_nvcsw	  the number of times a context switch resulted due to a process voluntarily giving up the processor before its time slice was
		  completed (usually to await availability of a resource).

     ru_nivcsw	  the number of times a context switch resulted due to a higher priority process becoming runnable or because the current process
		  exceeded its time slice.

NOTES

     The numbers ru_inblock and ru_oublock 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.

ERRORS

     Getrusage() returns -1 on error.  The possible errors are:

     [EINVAL]		The who parameter is not a valid value.

     [EFAULT]		The address specified by the rusage parameter is not in a valid part of the process address space.

SEE ALSO

     gettimeofday(2), wait(2)

BUGS

     There is no way to obtain information about a child process that has not yet terminated.

HISTORY

     The getrusage() function call appeared in 4.2BSD.

4th Berkeley Distribution					   June 4, 1993 					 4th Berkeley Distribution