mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.kernel.org, Rick Lindsley <ricklind@us.ibm.com>
Subject: Re: 2.5 io statistics?
Date: Tue, 8 Apr 2003 15:22:15 -0700	[thread overview]
Message-ID: <20030408152215.00b7beca.akpm@digeo.com> (raw)
In-Reply-To: <20030408155858.GB27912@work.bitmover.com>

Larry McVoy <lm@bitmover.com> wrote:
>
> Is there a writeup of the changes anywhere?  I'd like to port cstat to 2.5.
> Cstat is sort of a netstat/vmstat combo:
> 
> load free cach swap pgin  pgou dk0 dk1 dk2 dk3 ipkt opkt  int  ctx  usr sys idl
> 0.00  19M 562M  48M 4.0K   12K   0   0   0   0  137   25  267   83    0   0 100
> 0.00  18M 563M  48M   0    12K   0   0   0   0  133   22  258   77    0   1  99

It's currently undergoing a bit of change.

In 2.5.67 all IO activity is monitored by opening and reading
/sys/block/hda/stat.  This certainly doesn't scale when you have thousands of
disks, so there's a patch in -mm which performs runtime aggregation of global
stats and exposes that via /proc/diskstats.

So if you want to monitor the "global" IO activity, you don't need to open all
those sysfs files.

I don't know if the aggregate disk stats patch is ready to go yet.  I'm
awaiting testing results, conversion of userspace tools, etc.  I just plonked
it in there and haven't heard anything since.

As far as I know, neither the format of the sysfs file nor the format of
/proc/diskstats is documented anywhere.

Perhaps Rick can prepare a description for inclusion under Dcumentation/
somewhere?


  reply	other threads:[~2003-04-08 23:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 15:58 Larry McVoy
2003-04-08 22:22 ` Andrew Morton [this message]
2003-04-08 23:57   ` Rick Lindsley
2003-04-09  1:37   ` Larry McVoy
2003-04-15  5:17     ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030408152215.00b7beca.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=ricklind@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®