All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	benoit.canet@irqsave.net, qemu-devel@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3] block: Introduce "null" driver
Date: Fri, 29 Aug 2014 08:55:00 +0800	[thread overview]
Message-ID: <20140829005500.GD4196@T430.redhat.com> (raw)
In-Reply-To: <53FFABDB.2000609@redhat.com>

On Thu, 08/28 16:23, Eric Blake wrote:
> 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.

I'll add null-co to the list. But this list is a bit far from alphabetical:

archipelago, ..., vvfat, blkdebug,...

> 
> >  
> >  ##
> >  # @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

Will add.

Thanks,
Fam

  reply	other threads:[~2014-08-29  0:55 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
2014-08-29  0:55   ` Fam Zheng [this message]
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=20140829005500.GD4196@T430.redhat.com \
    --to=famz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=benoit.canet@irqsave.net \
    --cc=eblake@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 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.