From: Mike Fedyk <mfedyk@matchmail.com>
To: Manik Raina <manik@cisco.com>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: adding counters to count bytes read/written
Date: Mon, 20 May 2002 11:32:27 -0700 [thread overview]
Message-ID: <20020520183227.GB502@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0205201506240.14394-100000@localhost.localdomain> <20020520131222.K9955@mea-ext.zmailer.org> <3CE8D80C.3A771CB1@cisco.com>
On Mon, May 20, 2002 at 04:33:40PM +0530, Manik Raina wrote:
>
> Thanks for the comments Matti, Please see inline ...
>
> Matti Aarnio wrote:
> >
> > On Mon, May 20, 2002 at 03:09:36PM +0530, Manik Raina wrote:
> > > Hi Linus,
> > >
> > > This patch adds 2 counters to the task_struct for
> > > counting how many bytes were read/written using
> > > the read()/write() system calls.
> > >
> > > These counters may be useful in determining how
> > > many IO requests are made by each process.
> >
> > These are defined as UINTegers, are you sure that is appropriate type ?
> > What to do when they will overflow ? For short term activity tracking
> > they may be ok (4GB/200 MB/sec = 20 sec to wrap around), but for accounting
> > the overflow might not be liked thing..
>
>
> How about 64 bit counters ? i feel those should go on without
> wraparound for a _very_ long time.
I really doubt that 64bit counters in a fast path will be accepted. You'll
really need to justify something like that.
Have you looked at the process accounting code?
next prev parent reply other threads:[~2002-05-20 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 9:39 [PATCH]: adding counters to count bytes read/written Manik Raina
2002-05-20 10:12 ` Matti Aarnio
2002-05-20 11:03 ` Manik Raina
2002-05-20 18:32 ` Mike Fedyk [this message]
2002-05-20 18:51 ` Matti Aarnio
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=20020520183227.GB502@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manik@cisco.com \
--cc=matti.aarnio@zmailer.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