Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!genrad!mit-eddie!godot!harvard!seismo!umcp-cs!chris From: chris@umcp-cs.UUCP (Chris Torek) Newsgroups: net.unix-wizards Subject: Re: Need the equiv. of SYSINFO data under 4.2 Message-ID: <2472@umcp-cs.UUCP> Date: Sun, 13-Jan-85 19:51:41 EST Article-I.D.: umcp-cs.2472 Posted: Sun Jan 13 19:51:41 1985 Date-Received: Wed, 16-Jan-85 04:36:46 EST References: <7264@brl-tgr.ARPA> Organization: U of Maryland, Computer Science Dept., College Park, MD Lines: 33 > I need the page buffer statistics bread and lread (buffer reads, > logical reads) that are available from SV UNIX in the SYSINFO > structure. I'm not sure what you mean by ``page buffer statistics'', but all the per-process resource usage statistics in 4.2BSD are declared in the files. The paging statistics are kept in long ru_minflt; /* page reclaims */ long ru_majflt; /* page faults */ and long ru_nswap; /* swaps */ The block I/O system statistics are kept in long ru_inblock; /* block input operations */ long ru_oublock; /* block output operations */ There is no separate field for read-ahead cache hits; processes must pay for their read-ahead blocks even if they never use them. The resource usage stuff is obtained through the wait3() system call (see man 2 wait). If you are trying to analyze the buffer cache hit ratio, you can use the (undocumented) vtrace() system call to enable the cache trace points, if your kernel was compiled with -DTRACE. -- (This line accidently left nonblank.) In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690) UUCP: {seismo,allegra,brl-bmd}!umcp-cs!chris CSNet: chris@umcp-cs ARPA: chris@maryland