All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	Olaf Hering <olaf@aepfle.de>, <xen-devel@lists.xen.org>,
	<boris.ostrovsky@oracle.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH v2] xen-blkfront: remove type check from blkfront_setup_discard
Date: Mon, 13 Jan 2014 13:45:56 +0000	[thread overview]
Message-ID: <52D3EE14.3080609@citrix.com> (raw)
In-Reply-To: <52D3F535020000780011311B@nat28.tlf.novell.com>

On 13/01/14 13:16, Jan Beulich wrote:
>>>> On 13.01.14 at 14:00, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>> On Mon, 2014-01-13 at 12:34 +0000, Jan Beulich wrote:
>>>>>> On 13.01.14 at 13:01, Olaf Hering <olaf@aepfle.de> wrote:
>>>> On Mon, Jan 13, Jan Beulich wrote:
>>>>
>>>>> You can't do this in one go - the first two and the last one may be
>>>>> set independently (and are independent in their meaning), and
>>>>> hence need to be queried independently (xenbus_gather() fails
>>>>> on the first absent value).
>>>>
>>>> Yes, thats the purpose. Since the properties are required its an all or
>>>> nothing thing. If they are truly optional then blkif.h should be updated
>>>> to say that.
>>>
>>> They _are_ optional.
>>
>> But is it true that either they are all present or they are all absent?
> 
> No, it's not. discard-secure is independent of the other two (but
> those other two are tied together).

Can we have a patch to blkif.h that clarifies this?

e.g.,

feature-discard

   ...

   discard-granularity and discard-offset must also be present if
   feature-discard is enabled

   discard-secure may also be present if feature-discard is enabled.

David

  parent reply	other threads:[~2014-01-13 13:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 10:14 [PATCH v2] xen-blkfront: remove type check from blkfront_setup_discard Olaf Hering
2014-01-13 11:24 ` [Xen-devel] " Jan Beulich
2014-01-13 12:01   ` Olaf Hering
2014-01-13 12:34     ` Jan Beulich
2014-01-13 12:40       ` Olaf Hering
2014-01-13 12:40       ` [Xen-devel] " Olaf Hering
2014-01-13 13:00       ` Ian Campbell
2014-01-13 13:00       ` [Xen-devel] " Ian Campbell
2014-01-13 13:16         ` Jan Beulich
2014-01-13 13:16         ` [Xen-devel] " Jan Beulich
2014-01-13 13:34           ` Ian Campbell
2014-01-13 13:34           ` [Xen-devel] " Ian Campbell
2014-01-13 13:45           ` David Vrabel [this message]
2014-01-13 13:58             ` Jan Beulich
2014-01-13 15:57               ` Konrad Rzeszutek Wilk
2014-01-13 15:57               ` [Xen-devel] " Konrad Rzeszutek Wilk
2014-01-13 13:58             ` Jan Beulich
2014-01-14 14:53             ` Olaf Hering
2014-01-14 14:53             ` [Xen-devel] " Olaf Hering
2014-01-14 15:17               ` David Vrabel
2014-01-14 15:17               ` David Vrabel
2014-01-13 13:45           ` David Vrabel
2014-01-13 12:34     ` Jan Beulich
2014-01-13 12:01   ` Olaf Hering
2014-01-13 11:24 ` Jan Beulich

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=52D3EE14.3080609@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xen.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.