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] Tapdisk2 problem

On Sun, Aug 15, 2010 at 09:48:45PM +0100, Keir Fraser wrote:
> On 15/08/2010 21:36, "Daniel Stodden" <daniel.stodden@xxxxxxxxxx> wrote:
> 
> > On Sun, 2010-08-15 at 16:28 -0400, Keir Fraser wrote:
> >> On 15/08/2010 20:35, "Daniel Stodden" <daniel.stodden@xxxxxxxxxx> wrote:
> >> 
> >>> The problem is that the kernel has those changes. What's going to happen
> >>> is that if tapdisk2 anticipates the ring 'message' at offset 17, not 16
> >>> as intended, it will fail to find/clear the ring message, while the
> >>> kernel will keep it spinning through select(), and that's what you're
> >>> seeing.
> >>> 
> >>> Keir, okay to just pull that stuff?
> >> 
> >> What stuff to where?
> > 
> > changeset:   21707:feee0abed6aa
> > user:        Keir Fraser <keir.fraser@xxxxxxxxxx>
> > date:        Fri Jul 02 18:58:02 2010 +0100
> > summary:     blktap2: make protocol specific usage of shared sring
> > explicit
> > 
> > Into 4.0.1.
> 
> Okay, done.
> 

Btw will there be -rc7 now with these changes? 

-- Pasi



>  K.
> 
> > The offsets were broken by
> > 
> > changeset:   20267:e9366bed077e
> > user:        Keir Fraser <keir.fraser@xxxxxxxxxx>
> > date:        Thu Oct 01 12:27:01 2009 +0100
> > summary:     VNIF: Using smart polling instead of event notification.
> > 
> > Not so good?
> 
> > Daniel
> > 
> > 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>