All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wouter Verhelst <w@uter.be>
To: Kevin Wolf <kwolf@redhat.com>
Cc: nbd-general@lists.sourceforge.net, xieyingtai@huawei.com,
	subo7@huawei.com, qemu-block@nongnu.org, qemu-devel@nongnu.org,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [Nbd] [Qemu-block] [PATCH] doc: Propose NBD_FLAG_INIT_ZEROES extension
Date: Tue, 13 Dec 2016 13:18:56 +0100	[thread overview]
Message-ID: <20161213121856.b7fmjwjfkoeufz4g@grep.be> (raw)
In-Reply-To: <20161213073812.GA4443@noname.str.redhat.com>

On Tue, Dec 13, 2016 at 08:38:12AM +0100, Kevin Wolf wrote:
> Am 12.12.2016 um 19:12 hat Wouter Verhelst geschrieben:
> > I'm not opposed to this proposal, per se, but there seems to be some
> > disagreement (by Kevin, for instance) on whether this extension is at
> > all useful.
> 
> FWIW, I'm not opposed to adding the flag. I don't think it can hurt, but
> I wanted to ask the question so that we don't end up adding a feature
> that noone actually uses. Ultimately it's your call as a maintainer
> anyway how conservative you want to be with spec additions.

I'm not opposed either, but I do agree with you that we shouldn't add
such a feature if it doesn't end up getting used. Especially so if it
burns a flag in the (16-bit) "transmission flags" field, where space is
at a premium.

-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
       people in the world who think they really understand all of its rules,
       and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12

  reply	other threads:[~2016-12-13 12:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 23:42 [Qemu-devel] [PATCH] doc: Propose NBD_FLAG_INIT_ZEROES extension Eric Blake
2016-12-06  8:46 ` [Qemu-devel] [Nbd] " Alex Bligh
2016-12-06 10:30   ` Alex Bligh
2016-12-06  9:25 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2016-12-06 10:29   ` [Qemu-devel] [Nbd] " Alex Bligh
2016-12-06 15:21   ` [Qemu-devel] " Eric Blake
2016-12-07 10:44     ` Kevin Wolf
2016-12-07 15:50       ` Eric Blake
2016-12-07 16:35         ` Kevin Wolf
2016-12-06 10:18 ` [Qemu-devel] " Stefan Hajnoczi
2016-12-12 18:12 ` [Qemu-devel] [Nbd] " Wouter Verhelst
2016-12-13  7:38   ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2016-12-13 12:18     ` Wouter Verhelst [this message]
2016-12-13 13:19       ` [Qemu-devel] [Nbd] [Qemu-block] " Alex Bligh
2016-12-13 22:36       ` Eric Blake
2016-12-14  8:22         ` Wouter Verhelst
2016-12-14 16:37           ` Eric Blake
2016-12-14 16:54             ` Alex Bligh
2016-12-14 19:58             ` Wouter Verhelst

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=20161213121856.b7fmjwjfkoeufz4g@grep.be \
    --to=w@uter.be \
    --cc=kwolf@redhat.com \
    --cc=nbd-general@lists.sourceforge.net \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=subo7@huawei.com \
    --cc=xieyingtai@huawei.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.