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 3/7] pvSCSI driver

> > > However, this version went back to simple 1 ring architecture as same
> > > as VBD. We expect the performance will not be degraded because many
> > > transactions are distributed into multiple-rings.
> > I'm not quite sure what you mean here.  You currently have a single
> > ring per LUN; are you expecting heavy workloads to always be spread
> > over several LUNs?
> Our focussing domain is (was?) such an environment. However, it's not
> only one as you mentioned. I understood that we have to improve
> performance for each LUN access.
Thanks.

> > > We would like to enhance it as second step after this version is
> > > merged into Xen tree, if possible.
> > As Ian points out, stuff in the stable trees is supposed to have a
> > stable ABI, which can make some changes difficult.
> > 
> > Of course, we might be able to declare the tree stable except for SCSI
> > support, but that's a bit of a change from our current model.
> I would like to merge our pvSCSI code into Xen tree. Therefore, I am
> going to fix the code according to many comments I received. Could you
> teach me the deadline of fixing the code? (Someone wrote previous mail
> maybe...)
I think the 3.3 release is planned for late June, so you've got plenty
of time.

Steven.

Attachment: signature.asc
Description: Digital signature

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