From: Frank Schaefer <frank.schafer@setuza.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: counters
Date: 17 May 2002 12:47:53 +0200 [thread overview]
Message-ID: <1021632473.250.1.camel@ADMIN> (raw)
In-Reply-To: <3CE4C895.EB34A245@cisco.com>
On Fri, 2002-05-17 at 11:08, Manik Raina wrote:
>
> 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.
Hi Manik
and sorry that I read only half of your initial post.
I had a quick look at fs/read_write.c.
I don't see any hook in the functions here, to perform such a task. And
here this should belong to -- shouldn't it?
the functions could add ``count'' to the procfs entry of ``current''.
(just a thought) This info could be valuable - I think - if it wouldn't
make a large performance issue.
Regards
Frank
next prev parent reply other threads:[~2002-05-17 10:47 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 ` Frank Schaefer [this message]
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=1021632473.250.1.camel@ADMIN \
--to=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 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.