From: Max Reitz <mreitz@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 1/9] block: Add COR filter driver
Date: Fri, 20 Apr 2018 15:21:32 +0200 [thread overview]
Message-ID: <c22e1481-9a9f-71af-938c-f3f5254959d4@redhat.com> (raw)
In-Reply-To: <20180420083138.GK15181@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
On 2018-04-20 10:31, Stefan Hajnoczi wrote:
> On Mon, Apr 16, 2018 at 06:58:41PM +0200, Max Reitz wrote:
>> { 'enum': 'BlockdevDriver',
>> - 'data': [ 'blkdebug', 'blkverify', 'bochs', 'cloop',
>> + 'data': [ 'blkdebug', 'blkverify', 'bochs', 'cloop', 'cor',
>
> "copy-on-read" would be clearer than "cor" for the QMP API and the
> block/cor.c source file. Is there a need to make the name very short?
There definitely is no need. I decided I'd prefer to type less in the
test cases, so I went for the shorter name. (I thought blockdev-add was
sufficiently verbose as it is.)
But I don't mind un-abbreviating it either. (Probably better
considering that blockdev-add is already verbose, so there is no point
in making parts of it artificially dense.)
Thanks for reviewing!
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-04-20 13:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 16:58 [Qemu-devel] [PATCH 0/9] block: Add COR filter driver Max Reitz
2018-04-16 16:58 ` [Qemu-devel] [PATCH 1/9] " Max Reitz
2018-04-20 8:31 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-20 13:21 ` Max Reitz [this message]
2018-04-16 16:58 ` [Qemu-devel] [PATCH 2/9] block: BLK_PERM_WRITE includes ..._UNCHANGED Max Reitz
2018-04-20 8:32 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-20 12:04 ` Alberto Garcia
2018-04-20 13:22 ` Max Reitz
2018-04-16 16:58 ` [Qemu-devel] [PATCH 3/9] block: Add BDRV_REQ_WRITE_UNCHANGED flag Max Reitz
2018-04-20 8:33 ` Stefan Hajnoczi
2018-04-20 12:06 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2018-04-16 16:58 ` [Qemu-devel] [PATCH 4/9] block: Set BDRV_REQ_WRITE_UNCHANGED for COR writes Max Reitz
2018-04-20 8:33 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-20 12:06 ` Alberto Garcia
2018-04-16 16:58 ` [Qemu-devel] [PATCH 5/9] block/quorum: Support BDRV_REQ_WRITE_UNCHANGED Max Reitz
2018-04-20 8:44 ` Stefan Hajnoczi
2018-04-20 12:09 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2018-04-16 16:58 ` [Qemu-devel] [PATCH 6/9] block: Support BDRV_REQ_WRITE_UNCHANGED in filters Max Reitz
2018-04-20 8:35 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-20 12:19 ` Alberto Garcia
2018-04-16 16:58 ` [Qemu-devel] [PATCH 7/9] iotests: Clean up wrap image in 197 Max Reitz
2018-04-20 8:38 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-20 12:20 ` Alberto Garcia
2018-04-16 16:58 ` [Qemu-devel] [PATCH 8/9] iotests: Copy 197 for COR filter driver Max Reitz
2018-04-20 8:38 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-16 16:58 ` [Qemu-devel] [PATCH 9/9] iotests: Add test for COR across nodes Max Reitz
2018-04-20 8:43 ` Stefan Hajnoczi
2018-04-20 13:22 ` Max Reitz
2018-04-20 7:49 ` [Qemu-devel] [PATCH 0/9] block: Add COR filter driver Stefan Hajnoczi
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=c22e1481-9a9f-71af-938c-f3f5254959d4@redhat.com \
--to=mreitz@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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).