From: Luiz Capitulino <lcapitulino@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: aliguori@us.ibm.com, stefanha@linux.vnet.ibm.com,
jcody@redhat.com, qemu-devel@nongnu.org, fsimonce@redhat.com,
Paolo Bonzini <pbonzini@redhat.com>,
eblake@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/6] Mirrored writes using blockdev-transaction
Date: Thu, 1 Mar 2012 13:43:27 -0300 [thread overview]
Message-ID: <20120301134327.497fed02@doriath.home> (raw)
In-Reply-To: <4F4FA13C.6030307@redhat.com>
On Thu, 01 Mar 2012 17:18:04 +0100
Kevin Wolf <kwolf@redhat.com> wrote:
> Am 01.03.2012 17:02, schrieb Luiz Capitulino:
> > On Thu, 1 Mar 2012 12:21:42 +0100
> > Paolo Bonzini <pbonzini@redhat.com> wrote:
> >
> >> This implements all ingredients to establish mirrored writes.
> >
> > This looks good to me. I just have two comments:
> >
> > 1. I'm wondering if it would make more sense to have this transaction
> > operation in qmp instead of the block layer. Looks more complex to do though,
> > so I'm ok with this implementation
>
> Depends on what you're thinking of. Renaming the command to just
> 'transaction' and allowing anything to be added to the union wouldn't be
> very complex.
>
> The one thing we would need to change in order to make it generally
> useful is to move the actual logic into prepare/commit/abort handlers. I
> discussed this with Paolo on IRC and I think the conclusion was that for
> now the approach in the patches is good enough, but in the long run
> we'll switch. It doesn't affect external interfaces, so we can do it
> whenever we like.
Yes, that's what I called "transaction operation in qmp", but I don't mind
accepting this one and deferring the more complex idea to the future.
next prev parent reply other threads:[~2012-03-01 16:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 11:21 [Qemu-devel] [PATCH v2 0/6] Mirrored writes using blockdev-transaction Paolo Bonzini
2012-03-01 11:21 ` [Qemu-devel] [PATCH v2 1/6] fix format name for backing file Paolo Bonzini
2012-03-01 11:21 ` [Qemu-devel] [PATCH v2 2/6] qapi: complete implementation of unions Paolo Bonzini
2012-03-01 13:52 ` Kevin Wolf
2012-03-01 15:56 ` Luiz Capitulino
2012-03-01 11:21 ` [Qemu-devel] [PATCH v2 3/6] rename blockdev-group-snapshot-sync Paolo Bonzini
2012-03-01 11:21 ` [Qemu-devel] [PATCH v2 4/6] add reuse field Paolo Bonzini
2012-03-01 11:21 ` [Qemu-devel] [PATCH v2 5/6] Add blkmirror block driver Paolo Bonzini
2012-03-01 11:21 ` [Qemu-devel] [PATCH v2 6/6] add mirroring to blockdev-transaction Paolo Bonzini
2012-03-01 16:02 ` [Qemu-devel] [PATCH v2 0/6] Mirrored writes using blockdev-transaction Luiz Capitulino
2012-03-01 16:18 ` Kevin Wolf
2012-03-01 16:43 ` Luiz Capitulino [this message]
2012-03-01 21:10 ` Anthony Liguori
2012-03-01 21:30 ` Eric Blake
2012-03-01 21:36 ` Anthony Liguori
2012-03-02 13:05 ` Anthony Liguori
2012-03-05 8:53 ` Kevin Wolf
2012-03-05 9:28 ` Paolo Bonzini
2012-03-05 12:13 ` Kevin Wolf
2012-03-05 13:05 ` Paolo Bonzini
2012-03-05 14:47 ` Anthony Liguori
2012-03-05 14:54 ` 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=20120301134327.497fed02@doriath.home \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=eblake@redhat.com \
--cc=fsimonce@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).