public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
Cc: linux-kernel@vger.kernel.org, Jay Lan <jlan@engr.sgi.com>
Subject: Re: [patch 2.6.8.1] BSD accounting: update chars transferred value
Date: Wed, 8 Sep 2004 10:17:04 +0100	[thread overview]
Message-ID: <20040908101704.A29949@infradead.org> (raw)
In-Reply-To: <20040908090657.GA9879@frec.bull.fr>; from guillaume.thouvenin@bull.net on Wed, Sep 08, 2004 at 11:06:57AM +0200

On Wed, Sep 08, 2004 at 11:06:57AM +0200, Guillaume Thouvenin wrote:
> Hello,
> 
>   The goal of this patch is to improve BSD accounting by using what 
> is done in the CSA into BSD accounting. The final goal is to have a
> uniform accounting structure. 
> 
>   This patch updates information given by BSD accounting concerning
> bytes read and written. A field is already present in the BSD accounting
> structure but it is never updated. We don't add information about blocks
> read and written because, as it was discussed in previous email, the 
> information is inaccurate. Most writes which are flushed delayed would 
> get accounted to pdflushd. Thus, one solution to get this kind of 
> information is to add counters when the write back is performed. The 
> problem is that we don't know how to get information about the IID at 
> the page level (ie from struct page). So we remove this information for 
> the moment and it will be provided in another patch.
> 
> Changelog:
>   
>   - Adds two counters in the task_struct (rchar, wchar)
>   - Init fields during the creation of the process (during the fork)
>   - File I/O operations are done through sys_read(), sys_write(), 
>     sys_readv(), sys_writev() and sys_sendfile(). Thus we increment 
>     counters into those functions except with sys_sendfile(). For the
>     latter, the incrementation is done in the do_sendfile() because this
>     routine be directly called from the return of sys_sendfile().

I think it should be done in vfs_readv/vfs_write.  Else we'll miss the
updates from inekrnel consumers like nfsd.


  reply	other threads:[~2004-09-08  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08  9:06 [patch 2.6.8.1] BSD accounting: update chars transferred value Guillaume Thouvenin
2004-09-08  9:17 ` Christoph Hellwig [this message]
2004-09-08 11:02   ` Guillaume Thouvenin
  -- strict thread matches above, loose matches on Subject: below --
2004-09-08 11:29 Guillaume Thouvenin
2004-09-10 23:10 ` Jay Lan
2004-09-13  6:34   ` Guillaume Thouvenin
2004-09-14  0:00     ` Jay Lan

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=20040908101704.A29949@infradead.org \
    --to=hch@infradead.org \
    --cc=guillaume.thouvenin@bull.net \
    --cc=jlan@engr.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox