All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qapi: Add "backing" and "file" to BlockStats
Date: Wed, 22 Jan 2014 06:08:33 -0700	[thread overview]
Message-ID: <52DFC2D1.9060901@redhat.com> (raw)
In-Reply-To: <20140122093553.GB10065@dhcp-200-207.str.redhat.com>

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

On 01/22/2014 02:35 AM, Kevin Wolf wrote:
> Am 22.01.2014 um 04:30 hat Fam Zheng geschrieben:
>> Currently there is no way to query BlockStats of the backing chain. This
>> adds "backing" and "file" fields into BlockStats to make it possible.
>>
>> The old optional field "parent", which has the information for "file",
>> is kept there for backward compatibility, as an alias for "file".
>> However field name "file" is more consistent with "file" option name in
>> the block device configuration interface.
>>
>> Signed-off-by: Fam Zheng <famz@redhat.com>
> 
> I don't think it's a good idea to duplicate a field just because we like
> the new name better. Eric?

I concur - duplication for the sake of naming consistency doesn't add
any measurable benefit; I'd rather just improve the docs for the
existing name (libvirt will be forced to use the old name for
back-compat reasons anyway, making the new name useless cruft that just
makes the JSON longer and cost more cycles to parse then discard).

-- 
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:[~2014-01-22 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22  3:30 [Qemu-devel] [PATCH] qapi: Add "backing" and "file" to BlockStats Fam Zheng
2014-01-22  9:35 ` Kevin Wolf
2014-01-22 13:08   ` Eric Blake [this message]
2014-01-22 13:07 ` Eric Blake

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=52DFC2D1.9060901@redhat.com \
    --to=eblake@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@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.