From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
benoit.canet@irqsave.net, armbru@redhat.com,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] block: Introduce "null" driver
Date: Thu, 28 Aug 2014 16:23:23 -0600 [thread overview]
Message-ID: <53FFABDB.2000609@redhat.com> (raw)
In-Reply-To: <1409205191-11406-1-git-send-email-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2069 bytes --]
On 08/27/2014 11:53 PM, Fam Zheng wrote:
> This is an analogue to Linux null_blk. It can be used for testing block
> device emulation and general block layer functionalities such as
> coroutines and throttling, where disk IO is not necessary or wanted.
>
> Use null:// for AIO version, and null-co:// for coroutine version.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
>
> ---
> +++ b/qapi/block-core.json
> @@ -1150,7 +1150,8 @@
> 'data': [ 'archipelago', 'file', 'host_device', 'host_cdrom', 'host_floppy',
> 'http', 'https', 'ftp', 'ftps', 'tftp', 'vvfat', 'blkdebug',
> 'blkverify', 'bochs', 'cloop', 'cow', 'dmg', 'parallels', 'qcow',
> - 'qcow2', 'qed', 'raw', 'vdi', 'vhdx', 'vmdk', 'vpc', 'quorum' ] }
> + 'qcow2', 'qed', 'raw', 'vdi', 'vhdx', 'vmdk', 'vpc', 'quorum',
> + 'null' ] }
As mentioned elsewhere, you probably want 'null' AND 'null-co'. Bummer
that this list is mostly alphabetical, but that 'quorum' and 'null' are
out of order.
>
> ##
> # @BlockdevOptionsBase
> @@ -1203,6 +1204,19 @@
> 'data': { 'filename': 'str' } }
>
> ##
> +# @BlockdevOptionsNull
> +#
> +# Driver specific block device options for the null backend.
> +#
> +# @size: size of the device in bytes.
missing an #optional marker
> +#
> +# Since: 2.2
> +##
> +{ 'type': 'BlockdevOptionsNull',
> + 'base': 'BlockdevOptionsFile',
> + 'data': { '*size': 'int' } }
> +
> +##
> # @BlockdevOptionsVVFAT
> #
> # Driver specific block device options for the vvfat protocol.
> @@ -1484,7 +1498,8 @@
> 'vhdx': 'BlockdevOptionsGenericFormat',
> 'vmdk': 'BlockdevOptionsGenericCOWFormat',
> 'vpc': 'BlockdevOptionsGenericFormat',
> - 'quorum': 'BlockdevOptionsQuorum'
> + 'quorum': 'BlockdevOptionsQuorum',
> + 'null': 'BlockdevOptionsNull'
> } }
>
> ##
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-08-28 22:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 5:53 [Qemu-devel] [PATCH v3] block: Introduce "null" driver Fam Zheng
2014-08-28 15:22 ` Benoît Canet
2014-08-28 15:52 ` Eric Blake
2014-08-28 19:42 ` Paolo Bonzini
2014-08-28 22:15 ` Eric Blake
2014-08-28 22:21 ` Eric Blake
2014-08-29 0:45 ` Fam Zheng
2014-08-28 22:23 ` Eric Blake [this message]
2014-08-29 0:55 ` Fam Zheng
2014-08-29 6:48 ` Markus Armbruster
2014-09-03 11:10 ` Kevin Wolf
2014-09-03 12:34 ` Eric Blake
2014-09-03 12:48 ` Markus Armbruster
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=53FFABDB.2000609@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=benoit.canet@irqsave.net \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--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).