From: Jens Axboe <jens.axboe@oracle.com>
To: Nikanth Karthikesan <knikanth@suse.de>
Cc: dm-devel@redhat.com, Mark Landis <mark.landis@teradata.com>,
linux-kernel@vger.kernel.org, Alasdair G Kergon <agk@redhat.com>
Subject: Re: [RESEND] [PATCH linux-2.6-block#for-2.6.32] Seperate read and write statistics of in_flight requests
Date: Fri, 11 Sep 2009 09:17:53 +0200 [thread overview]
Message-ID: <20090911071753.GC18599@kernel.dk> (raw)
In-Reply-To: <200909110913.46769.knikanth@suse.de>
On Fri, Sep 11 2009, Nikanth Karthikesan wrote:
> Currently, there is a single in_flight counter measuring the number of
> requests in the request_queue. But some monitoring tools would like to
> know how many read requests and write requests are in progress. Split the
> current in_flight counter into two seperate counters for read and write.
>
> This information is exported as a sysfs attribute, as changing the
> currently available stat files would break the existing tools.
Applied, this is better than breaking existing stat exports.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: Nikanth Karthikesan <knikanth@suse.de>
Cc: Mark Landis <mark.landis@teradata.com>,
Alasdair G Kergon <agk@redhat.com>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [RESEND] [PATCH linux-2.6-block#for-2.6.32] Seperate read and write statistics of in_flight requests
Date: Fri, 11 Sep 2009 09:17:53 +0200 [thread overview]
Message-ID: <20090911071753.GC18599@kernel.dk> (raw)
In-Reply-To: <200909110913.46769.knikanth@suse.de>
On Fri, Sep 11 2009, Nikanth Karthikesan wrote:
> Currently, there is a single in_flight counter measuring the number of
> requests in the request_queue. But some monitoring tools would like to
> know how many read requests and write requests are in progress. Split the
> current in_flight counter into two seperate counters for read and write.
>
> This information is exported as a sysfs attribute, as changing the
> currently available stat files would break the existing tools.
Applied, this is better than breaking existing stat exports.
--
Jens Axboe
next prev parent reply other threads:[~2009-09-11 7:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 10:33 [PATCH] Seperate read and write statistics of in_flight requests Nikanth Karthikesan
2009-08-24 11:07 ` Jens Axboe
2009-08-24 12:24 ` Nikanth Karthikesan
2009-08-24 12:24 ` Nikanth Karthikesan
2009-09-11 3:43 ` [RESEND] [PATCH linux-2.6-block#for-2.6.32] " Nikanth Karthikesan
2009-09-11 3:43 ` Nikanth Karthikesan
2009-09-11 7:17 ` Jens Axboe [this message]
2009-09-11 7:17 ` Jens Axboe
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=20090911071753.GC18599@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=knikanth@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.landis@teradata.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 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.