From: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org, riel@redhat.com
Subject: Re: [Patch for review] BSD accounting IO stats
Date: Tue, 03 Aug 2004 13:20:01 +0200 [thread overview]
Message-ID: <410F74E1.9020400@bull.net> (raw)
In-Reply-To: <m3r7qpsoa4.fsf@averell.firstfloor.org>
Andi Kleen wrote:
>>diff -uprN -X dontdiff linux-2.6.8-rc2/drivers/block/ll_rw_blk.c linux-2.6.8-rc2+BSDacct_IO/drivers/block/ll_rw_blk.c
>>--- linux-2.6.8-rc2/drivers/block/ll_rw_blk.c 2004-07-18 06:57:42.000000000 +0200
>>+++ linux-2.6.8-rc2+BSDacct_IO/drivers/block/ll_rw_blk.c 2004-07-27 09:17:33.149321480 +0200
>>@@ -1949,10 +1949,12 @@ void drive_stat_acct(struct request *rq,
>>
>> if (rw == READ) {
>> disk_stat_add(rq->rq_disk, read_sectors, nr_sectors);
>>+ current->rblk += nr_sectors;
>>
>>
>
>This doesn't look very useful, because most writes which
>are flushed delayed would get accounted to pdflushd.
>Using such inaccurate data for accounting sounds quite dangerous
>to me.
>
>
I agree with that. Like you and Andrew said, this metric (write block)
is just an estimate (quite wrong indeed) of what really occurred in the
system because some writings are accounted elsewhere (pdflush or
journaling file system).
I also agree that a rough estimation is not very interesting, therefore
I'm working on another patch to provide accurate values.
Best,
Guillaume
next prev parent reply other threads:[~2004-08-03 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2oJkL-4sl-41@gated-at.bofh.it>
2004-08-02 12:44 ` [Patch for review] BSD accounting IO stats Andi Kleen
2004-08-02 19:11 ` Rik van Riel
2004-08-02 20:10 ` Chris Wedgwood
2004-08-03 11:20 ` Guillaume Thouvenin [this message]
2004-08-02 11:35 Guillaume Thouvenin
2004-08-02 12:13 ` Rik van Riel
2004-08-02 12:58 ` Guillaume Thouvenin
2004-08-02 16:57 ` Andrew Morton
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=410F74E1.9020400@bull.net \
--to=guillaume.thouvenin@bull.net \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/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