From: John Snow <jsnow@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: kwolf@redhat.com, xiecl.fnst@cn.fujitsu.com,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/7] blockjobs: preliminary refactoring work, Pt 1
Date: Wed, 26 Oct 2016 12:09:21 -0400 [thread overview]
Message-ID: <22e3cefa-6da8-d0ed-e675-1c0c92841e36@redhat.com> (raw)
In-Reply-To: <20161026045216.GH2677@localhost.localdomain>
On 10/26/2016 12:52 AM, Jeff Cody wrote:
> On Fri, Oct 14, 2016 at 02:32:55PM -0400, John Snow wrote:
>>
>>
>> On 10/13/2016 06:56 PM, John Snow wrote:
>>> This is a follow-up to patches 1-6 of:
>>> [PATCH v2 00/11] blockjobs: Fix transactional race condition
>>>
>>> That series started trying to refactor blockjobs with the goal of
>>> internalizing BlockJob state as a side effect of having gone through
>>> the effort of figuring out which commands were "safe" to call on
>>> a Job that has no coroutine object.
>>>
>>> I've split out the less contentious bits so I can move forward with my
>>> original work of focusing on the transactional race condition in a
>>> different series.
>>>
>>> Functionally the biggest difference here is the presence of "internal"
>>> block jobs, which do not emit QMP events or show up in block query
>>> requests. This is done for the sake of replication jobs, which should
>>> not be interfering with the public jobs namespace.
>>>
>>
>> I have v2 ready to send out correcting Kevin's comments in patch #01, but
>> I'd like to have the Replication maintainers at Fujitsu take a look at how I
>> have modified replication and at least 'ACK' the change.
>>
>> As a recap: I am creating "internal" block jobs that have no ID and
>> therefore do not collide with the user-specified jobs namespace. This way
>> users cannot query, cancel, pause, or otherwise accidentally interfere with
>> the replication job lifetime.
>>
>> It also means that management layers such as libvirt will not be aware of
>> the presence of such "internal" jobs.
>>
>> Relevant patches are 1-3. Please let me know if you have questions.
>>
>> Thanks,
>> --John Snow
>>
>
> Looks good to me, once you address Kevin's comments in patch 1.
>
Excellent, gracias.
>>
>>> ________________________________________________________________________________
>>>
>>> For convenience, this branch is available at:
>>> https://github.com/jnsnow/qemu.git branch job-refactor-pt1
>>> https://github.com/jnsnow/qemu/tree/job-refactor-pt1
>>>
>>> This version is tagged job-refactor-pt1-v1:
>>> https://github.com/jnsnow/qemu/releases/tag/job-refactor-pt1-v1
>>>
>>> John Snow (7):
>>> blockjobs: hide internal jobs from management API
>>> blockjobs: Allow creating internal jobs
>>> Replication/Blockjobs: Create replication jobs as internal
>>> blockjob: centralize QMP event emissions
>>> Blockjobs: Internalize user_pause logic
>>> blockjobs: split interface into public/private, Part 1
>>> blockjobs: fix documentation
>>>
>>> block/backup.c | 5 +-
>>> block/commit.c | 10 +-
>>> block/mirror.c | 28 +++--
>>> block/replication.c | 14 +--
>>> block/stream.c | 9 +-
>>> block/trace-events | 5 +-
>>> blockdev.c | 74 +++++--------
>>> blockjob.c | 109 ++++++++++++++----
>>> include/block/block.h | 3 +-
>>> include/block/block_int.h | 26 ++---
>>> include/block/blockjob.h | 257 +++++++------------------------------------
>>> include/block/blockjob_int.h | 232 ++++++++++++++++++++++++++++++++++++++
>>> qemu-img.c | 5 +-
>>> tests/test-blockjob-txn.c | 5 +-
>>> tests/test-blockjob.c | 4 +-
>>> 15 files changed, 443 insertions(+), 343 deletions(-)
>>> create mode 100644 include/block/blockjob_int.h
>>>
>
prev parent reply other threads:[~2016-10-26 16:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 22:56 [Qemu-devel] [PATCH 0/7] blockjobs: preliminary refactoring work, Pt 1 John Snow
2016-10-13 22:56 ` [Qemu-devel] [PATCH 1/7] blockjobs: hide internal jobs from management API John Snow
2016-10-14 12:58 ` Kevin Wolf
2016-10-14 17:32 ` John Snow
2016-10-13 22:56 ` [Qemu-devel] [PATCH 2/7] blockjobs: Allow creating internal jobs John Snow
2016-10-14 14:40 ` Kevin Wolf
2016-10-26 4:48 ` Jeff Cody
2016-10-13 22:56 ` [Qemu-devel] [PATCH 3/7] Replication/Blockjobs: Create replication jobs as internal John Snow
2016-10-14 14:40 ` Kevin Wolf
2016-10-26 4:48 ` Jeff Cody
2016-10-13 22:56 ` [Qemu-devel] [PATCH 4/7] blockjob: centralize QMP event emissions John Snow
2016-10-14 15:45 ` Kevin Wolf
2016-10-26 4:49 ` Jeff Cody
2016-10-13 22:57 ` [Qemu-devel] [PATCH 5/7] Blockjobs: Internalize user_pause logic John Snow
2016-10-14 15:46 ` Kevin Wolf
2016-10-26 4:50 ` Jeff Cody
2016-10-13 22:57 ` [Qemu-devel] [PATCH 6/7] blockjobs: split interface into public/private, Part 1 John Snow
2016-10-14 15:46 ` Kevin Wolf
2016-10-26 4:51 ` Jeff Cody
2016-10-13 22:57 ` [Qemu-devel] [PATCH 7/7] blockjobs: fix documentation John Snow
2016-10-14 15:46 ` Kevin Wolf
2016-10-26 4:51 ` Jeff Cody
2016-10-14 5:33 ` [Qemu-devel] [PATCH 0/7] blockjobs: preliminary refactoring work, Pt 1 no-reply
2016-10-14 18:32 ` John Snow
2016-10-26 4:52 ` Jeff Cody
2016-10-26 16:09 ` John Snow [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=22e3cefa-6da8-d0ed-e675-1c0c92841e36@redhat.com \
--to=jsnow@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=xiecl.fnst@cn.fujitsu.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).