From: Jerry Cooperstein <coop@axian.com>
To: Manik Raina <EED@ail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: counters
Date: Fri, 17 May 2002 07:52:35 -0700 [thread overview]
Message-ID: <20020517075235.A1680@p3.attbi.com> (raw)
In-Reply-To: <3CE3BECB.FF1AE6A@ail.com>
This is doable (some other OS's do it) but:
1) It requires some changes to the basic read/write call to gather
the statistics. It also requires stashing the counters somewhere
such as in the task_struct and thus requires modifying it.
2) It doesn't directly tell you about I/O statistics themselves
(which are available under /proc/stat) because the I/O request
may be gotten from cache, or may never be flushed from cache
to disk depending on subsequent events, so it will always
tend to overestimate the amount of real I/O done on the device.
Jerry Cooperstein <coop@axian.com>
Axian, Inc. Software Consulting and Training
4800 SW Griffith Dr., Ste. 202, Beaverton, OR 97005 USA
http://www.axian.com/
On Thu, May 16, 2002 at 07:44:35PM +0530, Manik Raina wrote:
> anyone knows if there are counters in the linux kernel
> which can be read via /proc like mechanism for the
> following :
>
> 1. total number of bytes read by process by syscalls
> like read()
>
> 2. total number of bytes written by each process by
> syscalls like write()
>
> thanks
> -
next prev parent reply other threads:[~2002-05-17 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 14:14 counters Manik Raina
2002-05-17 5:55 ` counters Frank Schaefer
2002-05-17 9:08 ` counters Manik Raina
2002-05-17 10:47 ` counters Frank Schaefer
2002-05-17 14:27 ` counters Manik Raina
2002-05-17 14:52 ` Jerry Cooperstein [this message]
2002-05-20 5:22 ` counters Frank Schaefer
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=20020517075235.A1680@p3.attbi.com \
--to=coop@axian.com \
--cc=EED@ail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.