qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org,
	Blue Swirl <blauwirbel@gmail.com>,
	ceph-devel@vger.kernel.org, Christian Brunner <chb@muc.de>
Subject: Re: [Qemu-devel] [RFC PATCH 1/1] ceph/rbd block driver for qemu-kvm
Date: Tue, 25 May 2010 08:25:00 -0500	[thread overview]
Message-ID: <4BFBCFAC.9070807@codemonkey.ws> (raw)
In-Reply-To: <4BFBB3C1.9020905@redhat.com>

On 05/25/2010 06:25 AM, Avi Kivity wrote:
> On 05/25/2010 02:02 PM, Kevin Wolf wrote:
>>
>>>
>>>> So could we not standardize a protocol for this that both sheepdog and
>>>> ceph could implement?
>>> The protocol already exists, nbd.  It doesn't support snapshotting etc.
>>> but we could extend it.
>>>
>>> But IMO what's needed is a plugin API for the block layer.
>> What would it buy us, apart from more downstreams and having to maintain
>> a stable API and ABI?
>
> Currently if someone wants to add a new block format, they have to 
> upstream it and wait for a new qemu to be released.  With a plugin 
> API, they can add a new block format to an existing, supported qemu.

Whether we have a plugin or protocol based mechanism to implement block 
formats really ends up being just an implementation detail.

In order to implement either, we need to take a subset of block 
functionality that we feel we can support long term and expose that.  
Right now, that's basically just querying characteristics (like size and 
geometry) and asynchronous reads and writes.

A protocol based mechanism has the advantage of being more robust in the 
face of poorly written block backends so if it's possible to make it 
perform as well as a plugin, it's a preferable approach.

Plugins that just expose chunks of QEMU internal state directly (like 
BlockDriver) are a really bad idea IMHO.

Regards,

Anthony Liguori

  parent reply	other threads:[~2010-05-25 13:25 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 19:22 [Qemu-devel] [RFC PATCH 1/1] ceph/rbd block driver for qemu-kvm Christian Brunner
2010-05-20 20:31 ` Blue Swirl
2010-05-20 21:18   ` Christian Brunner
2010-05-20 21:29     ` Anthony Liguori
2010-05-20 22:16       ` Christian Brunner
2010-05-21  5:28         ` Stefan Hajnoczi
2010-05-21  6:13           ` MORITA Kazutaka
2010-05-21  5:54         ` MORITA Kazutaka
2010-05-23 12:01       ` Avi Kivity
2010-05-24  7:12         ` MORITA Kazutaka
2010-05-24 11:05           ` Avi Kivity
2010-05-24 11:42             ` MORITA Kazutaka
2010-05-24 11:56               ` Avi Kivity
2010-05-24 12:07                 ` Cláudio Martins
2010-05-24 14:01                 ` MORITA Kazutaka
2010-05-24 19:07                   ` Christian Brunner
2010-05-24 19:38                     ` Anthony Liguori
2010-05-25  9:14                       ` Avi Kivity
2010-05-25 13:17                         ` Anthony Liguori
2010-05-25 13:25                           ` Avi Kivity
2010-05-25 13:29                             ` Anthony Liguori
2010-05-25 13:36                               ` Avi Kivity
2010-05-25 13:54                                 ` Anthony Liguori
2010-05-25 13:57                                   ` Avi Kivity
2010-05-25 14:02                                     ` Anthony Liguori
2010-05-26  8:44                                       ` Avi Kivity
2010-05-25 14:01                             ` Kevin Wolf
2010-05-25 16:21                               ` Avi Kivity
2010-05-25 17:12                                 ` Sage Weil
2010-05-26  5:24                                   ` MORITA Kazutaka
2010-05-26  8:46                                   ` Avi Kivity
2010-05-24 19:16                 ` Anthony Liguori
2010-05-25  9:19                   ` Avi Kivity
2010-05-25 13:26                   ` MORITA Kazutaka
2010-05-24  8:27         ` Stefan Hajnoczi
2010-05-24 11:03           ` Avi Kivity
2010-05-24 19:19             ` Anthony Liguori
2010-05-25  9:22               ` Avi Kivity
2010-05-25 11:02         ` Kevin Wolf
2010-05-25 11:25           ` Avi Kivity
2010-05-25 12:03             ` Christoph Hellwig
2010-05-25 12:13               ` Avi Kivity
2010-05-25 13:25             ` Anthony Liguori [this message]
2010-05-25 13:31               ` Avi Kivity
2010-05-25 13:35                 ` Anthony Liguori
2010-05-25 13:38                   ` Avi Kivity
2010-05-25 13:55                     ` Anthony Liguori
2010-05-25 14:01                       ` Avi Kivity
2010-05-25 14:05                         ` Anthony Liguori
2010-05-25 15:00                           ` Avi Kivity
2010-05-25 15:01                             ` Anthony Liguori
2010-05-25 16:16                               ` Avi Kivity
2010-05-25 16:21                                 ` Anthony Liguori
2010-05-25 16:27                                   ` Avi Kivity
2010-05-25 13:53               ` Kevin Wolf
2010-05-25 13:55                 ` Avi Kivity
2010-05-25 14:03                   ` Anthony Liguori
2010-05-25 15:02                     ` Avi Kivity
2010-05-25 14:09                   ` Kevin Wolf
2010-05-25 15:01                     ` Avi Kivity
2010-05-20 23:02   ` Yehuda Sadeh Weinraub
2010-05-23  7:59     ` Blue Swirl
2010-05-24  2:17       ` Yehuda Sadeh Weinraub
2010-05-25 20:13         ` Blue Swirl

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=4BFBCFAC.9070807@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=chb@muc.de \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).