From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-block@nongnu.org, Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 05/12] block: Introduce "drained begin/end" API
Date: Tue, 13 Oct 2015 13:12:46 +0200 [thread overview]
Message-ID: <20151013111246.GG4906@noname.str.redhat.com> (raw)
In-Reply-To: <561CDF53.3020404@redhat.com>
Am 13.10.2015 um 12:39 hat Paolo Bonzini geschrieben:
>
>
> On 13/10/2015 11:31, Kevin Wolf wrote:
> > This would mean that once you've sent an I/O request inside a drain
> > section, you have to expect that more internal I/O might be going on
> > after the request has completed. If you don't want this, you have to
> > issue another bdrv_drain() or use a nested bdrv_drained_begin/end()
> > section.
>
> Yes.
>
> > Sounds reasonable enough to me, but I guess this should be explicitly
> > documented.
>
> I agree. Perhaps bdrv_drained_begin/end() could be renamed to
> bdrv_drain_and_lock() / bdrv_unlock()?
It's not very obvious what bdrv_unlock() refers to, so I prefer the
current naming. Just making sure that the comment for bdrv_drained_begin
explains the exact semantics should be good enough.
Kevin
next prev parent reply other threads:[~2015-10-13 11:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 11:50 [Qemu-devel] [PATCH v2 00/12] block: bdrv_drained_begin/end for transactions on dataplane devices Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 01/12] aio: Add "is_external" flag for event handlers Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 02/12] nbd: Mark fd handlers client type as "external" Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 03/12] dataplane: Mark host notifiers' " Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 04/12] aio: introduce aio_{disable, enable}_external Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 05/12] block: Introduce "drained begin/end" API Fam Zheng
2015-10-12 13:59 ` Kevin Wolf
2015-10-12 14:27 ` Paolo Bonzini
2015-10-13 9:31 ` Kevin Wolf
2015-10-13 10:39 ` Paolo Bonzini
2015-10-13 11:12 ` Kevin Wolf [this message]
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 06/12] block: Add "drained begin/end" for transactional external snapshot Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 07/12] block: Add "drained begin/end" for transactional backup Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 08/12] block: Add "drained begin/end" for transactional blockdev-backup Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 09/12] block: Add "drained begin/end" for internal snapshot Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 10/12] block: Introduce BlockDriver.bdrv_drain callback Fam Zheng
2015-10-12 14:17 ` Kevin Wolf
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 11/12] qed: Implement .bdrv_drain Fam Zheng
2015-10-12 14:23 ` Kevin Wolf
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 12/12] tests: Add test case for aio_disable_external Fam Zheng
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=20151013111246.GG4906@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.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).