All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, jsnow@redhat.com, armbru@redhat.com,
	mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/5] block: Remove cache.writeback from blockdev-add
Date: Mon, 14 Mar 2016 10:10:34 -0600	[thread overview]
Message-ID: <56E6E27A.3080308@redhat.com> (raw)
In-Reply-To: <1457970292-12291-4-git-send-email-kwolf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]

On 03/14/2016 09:44 AM, Kevin Wolf wrote:
> The WCE bit is a frontend property and should not be part of the backend
> configuration. This is especially important because the same BDS can be
> used by different users with different WCE requirements.
> 
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>  qapi/block-core.json | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index 9bf1b22..e3617e2 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -1614,7 +1614,6 @@
>  #
>  # Includes cache-related options for block devices
>  #
> -# @writeback:   #optional enables writeback mode for any caches (default: true)
>  # @direct:      #optional enables use of O_DIRECT (bypass the host page cache;
>  #               default: false)
>  # @no-flush:    #optional ignore any flush requests for the device (default:
> @@ -1623,8 +1622,7 @@
>  # Since: 1.7
>  ##
>  { 'struct': 'BlockdevCacheOptions',
> -  'data': { '*writeback': 'bool',
> -            '*direct': 'bool',
> +  'data': { '*direct': 'bool',
>              '*no-flush': 'bool' } }

Observable through introspection.  Not quite backwards-compatible, but
at least clients can learn about it, and arguably clients shouldn't have
been using it.  I can accept it as a bug fix, even though it does risk
breaking old clients that were trying to use it.

If it helps, libvirt does not seem to have been using it.

-- 
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: 604 bytes --]

  reply	other threads:[~2016-03-14 16:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 15:44 [Qemu-devel] [PATCH 0/5] block: API changes for 2.6 Kevin Wolf
2016-03-14 15:44 ` [Qemu-devel] [PATCH 1/5] block: Remove copy-on-read from bdrv_move_feature_fields() Kevin Wolf
2016-03-14 15:51   ` Eric Blake
2016-03-14 15:44 ` [Qemu-devel] [PATCH 2/5] block: Remove dirty bitmaps " Kevin Wolf
2016-03-14 15:55   ` Eric Blake
2016-03-14 15:44 ` [Qemu-devel] [PATCH 3/5] block: Remove cache.writeback from blockdev-add Kevin Wolf
2016-03-14 16:10   ` Eric Blake [this message]
2016-03-14 16:22     ` Kevin Wolf
2016-03-14 15:44 ` [Qemu-devel] [PATCH 4/5] block: Make backing files always writeback Kevin Wolf
2016-03-14 16:46   ` Eric Blake
2016-03-14 15:44 ` [Qemu-devel] [PATCH 5/5] block: Reject writethrough mode except at the root Kevin Wolf
2016-03-14 16:50   ` Eric Blake
2016-03-18 17:10 ` [Qemu-devel] [PATCH 0/5] block: API changes for 2.6 Kevin Wolf

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=56E6E27A.3080308@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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.