On Fri, Mar 16, 2001 at 08:43:51 -0800, Alfred Perlstein wrote:
> * Sergey A. Osokin <[EMAIL PROTECTED]> [010316 08:27] wrote:
> > On Fri, Mar 16, 2001 at 09:27:30AM -0600, Dan Nelson wrote:
> > > In the last episode (Mar 16), Sergey A. Osokin said:
> > > > Hello, -currenters.
> > > >  
> > > > What do you think about add to libdevstat in/out/other statistics? I
> > > > think transfer great too, but sometimes that's not enough.  iostat
> > > > can't show read and write stats separatly, because compute_stats from
> > > > libdevstat simply sum up all results (in/out/other).
> > > 
> > > Struct devstat already has bytes_read and bytes_written per device, and
> > > the values are filled in (gkrellm seems to be able to get read/written
> > > stats just fine).
> > 
> > gkrellm good tool, but i don't want istall X/gtk/bla-bla-bla
> > on remote server. I want to use some CLI tool for it, like iostat
> > or somethink else.
> > 
> > Another idea?
> I think what he's saying is that libdevstat is OK, it's just that
> the tools that use it sum up the stats instead of displaying them
> inidividually.
> I would look at fixing iostat because libdevstat seems to provide
> all the data needed.

Alfred is correct.  All the data is there in the devstat structures,
you just have to subtract the current stats from the previous stats to get
what you want.

I suppose it would be possible to modify compute_stats() to include the
number of bytes read, written and freed, and the number of read, write,
free and other transactions.  I think that might kinda add to the interface
clutter, though.

This might be better implmented as a separate output mode to iostat(8).

If you (Sergey) write the code, send me the diffs, since I'm the maintainer
for both iostat and the devstat code.

Kenneth Merry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to