public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manik Raina <manik@cisco.com>
To: Frank Schaefer <frank.schafer@setuza.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: counters
Date: Fri, 17 May 2002 14:38:37 +0530	[thread overview]
Message-ID: <3CE4C895.EB34A245@cisco.com> (raw)
In-Reply-To: <3CE3BECB.FF1AE6A@ail.com> <1021614923.253.0.camel@ADMIN>


	Thanks for your response. What i meant was 
	every process could have an account of how
	many bytes were read/written to various
	filesystems/sockets using read()/write()
	system calls. 

	We could dump this stuff in /proc and
	it could tell us which processes are
	heavily IO bound.

	I am wondering if this information will
	be useful to anyone.

Frank Schaefer wrote:
> 
> On Thu, 2002-05-16 at 16:14, 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()
> 
> Hi,
> 
> as far as I know there's not a ready to use counter in the procfs.
> 
> BTW: What do you want to count? Do You mean timers?
> 
> It shouldn't be a problem, to write a little driver, which could make
> this available.
> 
> Regards
> Frank
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2002-05-17  9:08 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   ` Manik Raina [this message]
2002-05-17 10:47     ` counters Frank Schaefer
2002-05-17 14:27       ` counters Manik Raina
2002-05-17 14:52 ` counters Jerry Cooperstein
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=3CE4C895.EB34A245@cisco.com \
    --to=manik@cisco.com \
    --cc=frank.schafer@setuza.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox