public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Dronen <ndronen@frii.com>
To: Michael McLeod <michaelm@platypus.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: monitoring I/O
Date: Tue, 23 Jan 2001 17:58:25 -0700	[thread overview]
Message-ID: <20010123175825.A88907@frii.com> (raw)
In-Reply-To: <8494866EDB1D3E4F9C7E6AC2F95C259B01DA1C@plat.platypus.net>
In-Reply-To: <8494866EDB1D3E4F9C7E6AC2F95C259B01DA1C@plat.platypus.net>; from michaelm@platypus.net on Wed, Jan 24, 2001 at 11:52:36AM +1100

Check out the disk_io field in /proc/stat.

On Wed, Jan 24, 2001 at 11:52:36AM +1100, Michael McLeod wrote:
> Hello
> 
> I am hoping someone can give me a little information or point me in the
> right direction.  I would like to write an application that monitors I/O
> on a linux machine, but I need some help in determining where to get the
> information I'm looking for.  What I would like to do is 'hook' into the
> kernel and record information such as volume name, type of request (read
> or write), the amount of data being read or written, how long each
> transaction takes....  
> 
> Any help would be greatly appreciated, or if there is something like
> this already available that would be even better.  Thanx
> 
> Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-24  0:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24  0:52 monitoring I/O Michael McLeod
2001-01-24  0:58 ` Nicholas Dronen [this message]
2001-01-24 11:57   ` Daniel Kobras
2001-02-19 19:19 ` Karim Yaghmour
  -- strict thread matches above, loose matches on Subject: below --
2001-01-24 13:58 richardj_moore

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=20010123175825.A88907@frii.com \
    --to=ndronen@frii.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michaelm@platypus.net \
    /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