All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Nikanth Karthikesan <knikanth@suse.de>
Cc: Corrado Zoccolo <czoccolo@gmail.com>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND][PATCH linux-2.6-block#for-linus]  Seperate read and write statistics of in_flight requests v2
Date: Tue, 6 Oct 2009 20:17:13 +0200	[thread overview]
Message-ID: <20091006181713.GC5216@kernel.dk> (raw)
In-Reply-To: <200910061855.48502.knikanth@suse.de>

On Tue, Oct 06 2009, Nikanth Karthikesan wrote:
> [Sorry, resending as the previous mail was word-wrapped]
> 
> Commit a9327cac440be4d8333bba975cbbf76045096275 added seperate read
> and write statistics of in_flight requests. And exported the number
> of read and write requests in progress seperately through sysfs.
> 
> But  Corrado Zoccolo <czoccolo@gmail.com> reported getting strange
> output from "iostat -kx 2". Global values for service time and
> utilization were garbage. For interval values, utilization was always
> 100%, and service time is higher than normal.
> 
> So this was reverted by commit 0f78ab9899e9d6acb09d5465def618704255963b
> 
> The problem was in part_round_stats_single(), I missed the following:
>         if (now == part->stamp)
>                 return;
> 
> -       if (part->in_flight) {
> +       if (part_in_flight(part)) {
>                 __part_stat_add(cpu, part, time_in_queue,
>                                 part_in_flight(part) * (now - part->stamp));
>                 __part_stat_add(cpu, part, io_ticks, (now - part->stamp));
> 
> With this chunk included, the reported regression gets fixed.

Thanks, applied.

-- 
Jens Axboe


      reply	other threads:[~2009-10-06 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 13:25 [RESEND][PATCH linux-2.6-block#for-linus] Seperate read and write statistics of in_flight requests v2 Nikanth Karthikesan
2009-10-06 18:17 ` Jens Axboe [this message]

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=20091006181713.GC5216@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=czoccolo@gmail.com \
    --cc=knikanth@suse.de \
    --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.