qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Ming Lei <ming.lei@canonical.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Fam Zheng <famz@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/3] block: block: introduce bdrv_io_plug() and bdrv_io_unplug()
Date: Tue, 01 Jul 2014 18:56:13 +0200	[thread overview]
Message-ID: <53B2E82D.8020000@redhat.com> (raw)
In-Reply-To: <20140701152130.GK4587@noname.str.redhat.com>

Il 01/07/2014 17:21, Kevin Wolf ha scritto:
>>>> Does this bs->file forwarding work for more than the raw driver? For
>>>> example, if drv is an image format driver that needs to read some
>>>> metadata from the image before it can submit the payload, does this
>>>> still do what you were intending?
>>
>> Sorry for not understanding the problem, and you are right, these
>> patches can't support other formats, and for solving the dependency,
>> changes to image format driver should be needed.
>
> Then let's drop the bs->file recursion here and add an explicit
> .bdrv_io_plug/unplug callback to the raw driver.

Actually I thought about this in my review, and there's no reason for 
this not to work for image formats.

While bs->file is plugged, image formats will start executing their 
bdrv_co_readv/bdrv_co_writev callbacks, and issue reads or writes as 
necessary.  The reads and writes will accumulate in bs->file until it is 
unplugged, which is exactly the effect we want.

The change in bdrv_drain_all is ugly though.  I don't have a better 
idea, but I would like to understand better why it is needed.  Ming Lei, 
did you see a deadlock without it?

Paolo

  reply	other threads:[~2014-07-01 16:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01  7:51 [Qemu-devel] [PATCH v2 0/3] linux-aio: introduce submit I/O at batch Ming Lei
2014-07-01  7:51 ` [Qemu-devel] [PATCH v2 1/3] block: block: introduce bdrv_io_plug() and bdrv_io_unplug() Ming Lei
2014-07-01 11:18   ` Kevin Wolf
2014-07-01 13:31     ` Ming Lei
2014-07-01 14:39       ` Ming Lei
2014-07-01 15:21         ` Kevin Wolf
2014-07-01 16:56           ` Paolo Bonzini [this message]
2014-07-02  0:46             ` Ming Lei
2014-07-02  2:35               ` Ming Lei
2014-07-02  8:18               ` Paolo Bonzini
2014-07-02  8:38                 ` Kevin Wolf
2014-07-02  8:49                   ` Paolo Bonzini
2014-07-02  8:39                 ` Ming Lei
2014-07-02  8:56                   ` Paolo Bonzini
2014-07-02  9:12                     ` Kevin Wolf
2014-07-02  9:29                       ` Ming Lei
2014-07-02  9:49                         ` Kevin Wolf
2014-07-02 10:02                           ` Ming Lei
2014-07-02 10:24                             ` Paolo Bonzini
2014-07-02 10:28                               ` Ming Lei
2014-07-02  9:26                     ` Ming Lei
2014-07-01  7:51 ` [Qemu-devel] [PATCH v2 2/3] linux-aio: implement io plug and unplug Ming Lei
2014-07-01  7:51 ` [Qemu-devel] [PATCH v2 3/3] dataplane: submit I/O at batch Ming Lei

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=53B2E82D.8020000@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=ming.lei@canonical.com \
    --cc=mst@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).