WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] add placeholder for packet extension to block in

To: "Keir Fraser" <keir@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] add placeholder for packet extension to block interface
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Wed, 22 Dec 2010 11:55:14 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 22 Dec 2010 03:56:12 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C9378F3F.D835%keir@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4D11DCB30200007800029497@xxxxxxxxxxxxxxxxxx> <C9378F3F.D835%keir@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> On 22.12.10 at 12:19, Keir Fraser <keir@xxxxxxx> wrote:
> On 22/12/2010 10:10, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
> 
>> While the corresponding implementation has been in our trees for quite
>> a while, it's in a state that doesn't make it suitable for submission,
>> and the original author having left the company leaves open to find
>> someone to complete this work. Yet to prevent problems with other
>> interface extensions we'd like to keep the slot in the number space
>> reserved for the purpose it has been serving here.
>> 
>> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
>> 
>> --- a/xen/include/public/io/blkif.h
>> +++ b/xen/include/public/io/blkif.h
>> @@ -76,6 +76,10 @@
>>   * "feature-flush-cache" node!
>>   */
>>  #define BLKIF_OP_FLUSH_DISKCACHE   3
>> +/*
>> + * Device specific command packet contained within the request
>> + */
>> +#define BLKIF_OP_PACKET            4
> 
> Without more details, perhaps it would be better to call this
> BLKIF_OP_RESERVED_1 or BLKIF_OP_RESERVED_NOVELL. It makes it clearer what is
> going on (used internally by Novell for feature not yet submitted upstream),
> and the name can be changed to BLKIF_OP_PACKET if the support ever gets
> cleaned up and accepted.

How about this one then?

While the corresponding implementation has been in our trees for quite
a while, it's in a state that doesn't make it suitable for submission,
and the original author having left the company leaves open to find
someone to complete this work. Yet to prevent problems with other
interface extensions we'd like to keep the slot in the number space
reserved for the purpose it has been serving here.

Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>

--- a/xen/include/public/io/blkif.h
+++ b/xen/include/public/io/blkif.h
@@ -76,6 +76,11 @@
  * "feature-flush-cache" node!
  */
 #define BLKIF_OP_FLUSH_DISKCACHE   3
+/*
+ * Used in SLES sources for device specific command packet
+ * contained within the request. Reserved for that purpose.
+ */
+#define BLKIF_OP_RESERVED_1        4
 
 /*
  * Maximum scatter/gather segments per request.



Attachment: xen-blkif-op-packet-placeholder.patch
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>