From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH] Add tar container format
Date: Thu, 13 Aug 2009 18:13:27 -0500 [thread overview]
Message-ID: <4A849E17.3030901@codemonkey.ws> (raw)
In-Reply-To: <1F7A05E1-0B0B-4C68-B07B-2F36B9BECF81@suse.de>
Alexander Graf wrote:
>
>> I'd almost rather see something like gio integration so that this
>> sort of generic filesystem stuff could live somewhere else. I'm
>> curious what others think though. Does it seem reasonable to include
>> this type of functionality?
>
>
> A plugin infrastructure sounds nice at first, but doesn't do all the
> fedoras and ubuntus out there too much good ;-).
If we did plugins, it would not be a GPL-safe boundary so all plugins
would be forced to be GPL.
What's attractive about doing plugins for the block layer is that we
have a relatively stable interface for block drivers. The current AIO
ops should be good for a very long time so API churn shouldn't be a
major issue. The code is all pretty well isolated today.
As part of the longer term refactoring, I think it also makes sense to
split the block layer into a library that can be consumed independent of
QEMU. Obviously, folks want to make use of our block code who don't
care at all about QEMU. A lot of people use qemu-img for vmdk
manipulation, for instance. It also makes tools like qemu-iotest able
to consume the block layer in a saner way.
If others agree, I think we should start going down this road.
block-tar/block-dictzip seem like obvious candidates for plugins.
Regards,
Anthony Liguori
> Alex
next prev parent reply other threads:[~2009-08-13 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 15:33 [Qemu-devel] [PATCH] Add tar container format Alexander Graf
2009-08-13 22:57 ` Anthony Liguori
2009-08-13 23:08 ` Alexander Graf
2009-08-13 23:13 ` Anthony Liguori [this message]
2009-08-13 23:15 ` Anthony Liguori
2009-08-15 20:36 ` Christoph Hellwig
2009-08-17 12:05 ` [Qemu-devel] " 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=4A849E17.3030901@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=hch@lst.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.