From: Ming Lei <ming.lei@canonical.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Fam Zheng <famz@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1 1/3] block: block: introduce bdrv_io_plug() and bdrv_io_unplug()
Date: Tue, 1 Jul 2014 00:15:02 +0800 [thread overview]
Message-ID: <CACVXFVMfAk-CL9+mckEME2zgEPVCT=3VJh69baeXwmA26Xpttw@mail.gmail.com> (raw)
In-Reply-To: <53B18BF3.6020403@redhat.com>
On Tue, Jul 1, 2014 at 12:10 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> Il 30/06/2014 17:47, Ming Lei ha scritto:
>
>> From: Ming Lei <tom.leiming@gmail.com>
>>
>> This patch introduces these two APIs so that following
>> patches can support queuing I/O requests and submitting them
>> at batch for improving I/O performance.
>>
>> Signed-off-by: Ming Lei <ming.lei@canonical.com>
>> ---
>> block.c | 22 ++++++++++++++++++++++
>> include/block/block.h | 3 +++
>> include/block/block_int.h | 4 ++++
>> 3 files changed, 29 insertions(+)
>>
>> diff --git a/block.c b/block.c
>> index 217f523..2b4ec5b 100644
>> --- a/block.c
>> +++ b/block.c
>> @@ -1910,6 +1910,7 @@ void bdrv_drain_all(void)
>> bool bs_busy;
>>
>> aio_context_acquire(aio_context);
>> + bdrv_io_unplug(bs);
>> bdrv_start_throttled_reqs(bs);
>> bs_busy = bdrv_requests_pending(bs);
>> bs_busy |= aio_poll(aio_context, bs_busy);
>> @@ -5774,3 +5775,24 @@ bool bdrv_is_first_non_filter(BlockDriverState
>> *candidate)
>>
>> return false;
>> }
>> +
>> +void bdrv_io_plug(BlockDriverState *bs)
>> +{
>> + BlockDriver *drv = bs->drv;
>> + if (drv && drv->bdrv_io_plug) {
>> + drv->bdrv_io_plug(bs);
>> + } else if (bs->file) {
>> + bdrv_io_plug(bs->file);
>> + }
>> +}
>> +
>> +int bdrv_io_unplug(BlockDriverState *bs)
>> +{
>> + BlockDriver *drv = bs->drv;
>> + if (drv && drv->bdrv_io_unplug) {
>> + return drv->bdrv_io_unplug(bs);
>> + } else if (bs->file) {
>> + return bdrv_io_unplug(bs->file);
>> + }
>> + return 0;
>
>
> I think this should return void (and that's how you use it in patch 3
> indeed). If you fix this you can add my Reviewed-by tag.
It can be used to trace how many IO are submitted at batch,
otherwise device can't know this information at all.
Thanks,
--
Ming Lei
next prev parent reply other threads:[~2014-06-30 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 15:47 [Qemu-devel] [PATCH v1 0/3] linux-aio: introduce submit I/O at batch Ming Lei
2014-06-30 15:47 ` [Qemu-devel] [PATCH v1 1/3] block: block: introduce bdrv_io_plug() and bdrv_io_unplug() Ming Lei
2014-06-30 16:10 ` Paolo Bonzini
2014-06-30 16:15 ` Ming Lei [this message]
2014-06-30 16:18 ` Paolo Bonzini
2014-06-30 16:29 ` Ming Lei
2014-06-30 15:47 ` [Qemu-devel] [PATCH v1 2/3] linux-aio: implement io plug and unplug Ming Lei
2014-06-30 17:31 ` Paolo Bonzini
2014-07-01 1:05 ` Ming Lei
2014-07-01 6:16 ` Paolo Bonzini
2014-06-30 15:47 ` [Qemu-devel] [PATCH v1 3/3] dataplane: submit I/O at batch Ming Lei
2014-06-30 16:11 ` Paolo Bonzini
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='CACVXFVMfAk-CL9+mckEME2zgEPVCT=3VJh69baeXwmA26Xpttw@mail.gmail.com' \
--to=ming.lei@canonical.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).