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/
Home Products Support Community News


Re: [Xen-devel] [Patch 3/7] pvSCSI driver

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, Jun Kamada <kama@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [Patch 3/7] pvSCSI driver
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 28 Feb 2008 09:56:39 +0000
Cc: Steven Smith <Steven.Smith@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Santos, Jose Renato G" <joserenato.santos@xxxxxx>
Delivery-date: Thu, 28 Feb 2008 01:57:16 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <DD74FBB8EE28D441903D56487861CD9D297A95B9@xxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ach5whnldW35YQUKQyiLrY9BpSREjAAJ+EggAAGO0aw=
Thread-topic: [Xen-devel] [Patch 3/7] pvSCSI driver
User-agent: Microsoft-Entourage/
On 28/2/08 09:23, "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx> wrote:

>> In fact, previous version of pvSCSI driver used 2 rings for frontend
>> to backend and backend to frontend communication respectively. The
>> backend also queued requests from frontend and released the ring
>> immediately. This may be very similer concept to the Netchannel2.
> Cool, that sounds better. Did you still have fixed length command
> structs, or allow variable length messages? (I'm very keen we use the
> latter)

The netchannels2 model is 16-byte granularity 'cells' in the comms rings. A
descriptor can span multiple cells and its length is implicitly known from
its type (which resides in the first byte of the first cell). Individual
cells do not wrap in the ring (since the ring is a multiple of 16 bytes in
size) but multi-cell descriptors may wrap. Further, netchannel2 allows
descriptors to be chained into longer messages. I think Jose is going to use
the msb of the descriptor-identifier byte for this purpose.

We've toed-and-froed on details of this protocol a few times, so I've cc'ed
Jose in case the current state of the design is different from what I

 -- Keir

Xen-devel mailing list