From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: <kmo@daterainc.com>, <akpm@linux-foundation.org>,
<dm-devel@redhat.com>, <linux-kernel@vger.kernel.org>,
<linux-nvme@lists.infradead.org>, <drbd-user@lists.linbit.com>
Subject: Re: [PATCH 0/6] blk: introduce generic io stat accounting help function
Date: Tue, 25 Nov 2014 12:48:48 +0800 [thread overview]
Message-ID: <54740A30.8020105@cn.fujitsu.com> (raw)
In-Reply-To: <547348DE.60704@kernel.dk>
On 11/24/2014 11:03 PM, Jens Axboe wrote:
> On 11/23/2014 08:05 PM, Gu Zheng wrote:
>> Many block drivers accounting io stat based on bio (e.g. NVMe...),
>> the blk_account_io_start/end() which is based on request
>> does not make sense to them, so here we introduce the similar help
>> function named generic_start/end_io_acct base on raw sectors, and it can
>> simplify some driver's open io accounting code.
>>
>> Gu Zheng (6):
>> blk: introduce generic io stat accounting help function
>> NVMe: use generic io stat accounting functions to simplify
>> nvme_start/end_io_acct
>> md/bcache: use generic io stats accounting functions to simplify io
>> stat accounting
>> drbd: use generic io stats accounting functions to simplify io stat
>> accounting
>> md: use generic io stats accounting functions to simplify io stat
>> accounting
>> block/rsxx: use generic io stats accounting functions to simplify io
>> stat accounting
>
> Thanks, this looks good. I'll apply it, except 2/6, since nvme no longer uses them.
OK.
Thanks,
Gu
>
prev parent reply other threads:[~2014-11-25 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1416798327-12817-1-git-send-email-guz.fnst@cn.fujitsu.com>
[not found] ` <1416798327-12817-4-git-send-email-guz.fnst@cn.fujitsu.com>
2014-11-24 4:48 ` [PATCH 3/6] md/bcache: use generic io stats accounting functions to simplify io stat accounting Kent Overstreet
2014-11-24 15:03 ` [PATCH 0/6] blk: introduce generic io stat accounting help function Jens Axboe
2014-11-25 4:48 ` Gu Zheng [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=54740A30.8020105@cn.fujitsu.com \
--to=guz.fnst@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=drbd-user@lists.linbit.com \
--cc=kmo@daterainc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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