mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Chad Talbott <ctalbott@google.com>, ".A. Magallon" <jamagallon@able.es>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Stephen Tweedie <sct@redhat.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] ide-io.c, kernel 2.4.22 Fix for IO stats in /proc/partitions, was Re: sard/iostat disk I/O statistics/accounting for 2.5.8-pre3
Date: 24 Sep 2003 15:15:12 +0100	[thread overview]
Message-ID: <1064412912.21892.19.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <20030924092418.A28838@devserv.devel.redhat.com>

Hi,

On Wed, 2003-09-24, Chad Talbott wrote:


> Here's the one that I compiled and tested. It makes /proc/partitions
> report correctly.

Looks OK, but I'd defer to an IDE expert on the question of whether this
is the best fix or not.

Basically, you need to pair accounting start points with accounting end
points.  This patch removes the end point from the IDE special-command
postprocessing, but only by manually replacing end_that_request_last()
with a variant which doesn't do accounting.

I'd really rather see a patch which accounted for the start of the
special command in the first place (via "req_new_io()" when the special
request is first queued), as I suspect that might be a more robust way
of doing things.  But as I said, it would take somebody more familiar
with the IDE code to know whether that's really going to be better or
not.

Cheers,
 Stephen


       reply	other threads:[~2003-09-24 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030924092418.A28838@devserv.devel.redhat.com>
2003-09-24 14:15 ` Stephen C. Tweedie [this message]
2003-09-15 20:21 Chad Talbott
2003-09-21 22:47 ` J.A. Magallon
2003-09-23 18:09   ` Chad Talbott

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=1064412912.21892.19.camel@sisko.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ctalbott@google.com \
    --cc=jamagallon@able.es \
    --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

all inboxes | Powered by JetHome®