All of lore.kernel.org
 help / color / mirror / Atom feed
* BSoD with GPLPV + tap:aio
@ 2009-11-07 22:51 James Harper
  2009-11-07 22:54 ` James Harper
  2009-11-09 10:04 ` Paul Durrant
  0 siblings, 2 replies; 6+ messages in thread
From: James Harper @ 2009-11-07 22:51 UTC (permalink / raw)
  To: xen-devel

When I use my GPLPV drivers with tap:aio, I get a random BSoD after a
while, normally 0x0000000A.

Can anyone suggest what could be different with file|phy vs tap:aio that
might cause a problem? Is tap:aio otherwise known to be good?

Thanks

James

^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: BSoD with GPLPV + tap:aio
  2009-11-07 22:51 BSoD with GPLPV + tap:aio James Harper
@ 2009-11-07 22:54 ` James Harper
  2009-11-09 10:04 ` Paul Durrant
  1 sibling, 0 replies; 6+ messages in thread
From: James Harper @ 2009-11-07 22:54 UTC (permalink / raw)
  To: James Harper, xen-devel

> 
> When I use my GPLPV drivers with tap:aio, I get a random BSoD after a
> while, normally 0x0000000A.
> 
> Can anyone suggest what could be different with file|phy vs tap:aio
that
> might cause a problem? Is tap:aio otherwise known to be good?
> 

Forgot to add, the underlying file is sparse.

Thanks

James

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: BSoD with GPLPV + tap:aio
  2009-11-07 22:51 BSoD with GPLPV + tap:aio James Harper
  2009-11-07 22:54 ` James Harper
@ 2009-11-09 10:04 ` Paul Durrant
  2009-11-09 10:06   ` James Harper
  1 sibling, 1 reply; 6+ messages in thread
From: Paul Durrant @ 2009-11-09 10:04 UTC (permalink / raw)
  To: James Harper; +Cc: xen-devel@lists.xensource.com

James Harper wrote:
> When I use my GPLPV drivers with tap:aio, I get a random BSoD after a
> while, normally 0x0000000A.
> 
> Can anyone suggest what could be different with file|phy vs tap:aio that
> might cause a problem? Is tap:aio otherwise known to be good?
> 

I guess the main difference is likely to be blkback vs. blktap. Guessing 
from the minimal info., I'm guessing you're probably hitting a state 
model problem. Was there any significant PnP going on when you got the BSOD?

   Paul

-- 
===============================
Paul Durrant, Software Engineer
Citrix Systems (R&D) Ltd.
===============================

^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: BSoD with GPLPV + tap:aio
  2009-11-09 10:04 ` Paul Durrant
@ 2009-11-09 10:06   ` James Harper
  2009-11-09 10:13     ` Paul Durrant
  0 siblings, 1 reply; 6+ messages in thread
From: James Harper @ 2009-11-09 10:06 UTC (permalink / raw)
  To: Paul Durrant; +Cc: xen-devel

> 
> James Harper wrote:
> > When I use my GPLPV drivers with tap:aio, I get a random BSoD after
a
> > while, normally 0x0000000A.
> >
> > Can anyone suggest what could be different with file|phy vs tap:aio
that
> > might cause a problem? Is tap:aio otherwise known to be good?
> >
> 
> I guess the main difference is likely to be blkback vs. blktap.
Guessing
> from the minimal info., I'm guessing you're probably hitting a state
> model problem. Was there any significant PnP going on when you got the
BSOD?
> 

No PnP. I/O was being saturated though - I was performing a restore via
network to the disk on the machine that crashed.

Using phy: or file: I can restore 600GB with no problems at all. With
tap:aio it crashes after a few tens of GB.

James

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: BSoD with GPLPV + tap:aio
  2009-11-09 10:06   ` James Harper
@ 2009-11-09 10:13     ` Paul Durrant
  2009-11-09 10:15       ` James Harper
  0 siblings, 1 reply; 6+ messages in thread
From: Paul Durrant @ 2009-11-09 10:13 UTC (permalink / raw)
  To: James Harper; +Cc: xen-devel@lists.xensource.com

James Harper wrote:
> 
> No PnP. I/O was being saturated though - I was performing a restore via
> network to the disk on the machine that crashed.
> 
> Using phy: or file: I can restore 600GB with no problems at all. With
> tap:aio it crashes after a few tens of GB.
> 

Another guess then... tap will probably have more outstanding 
transactions than back as its datapath is likely to be longer and so is 
higher latency. Is your frontend overflowing a queue of outstanding SRBs?

   Paul

-- 
===============================
Paul Durrant, Software Engineer

Citrix Systems (R&D) Ltd.
First Floor, Building 101
Cambridge Science Park
Milton Road
Cambridge CB4 0FY
United Kingdom

TEL: x35957 (+44 1223 225957)
===============================

^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: BSoD with GPLPV + tap:aio
  2009-11-09 10:13     ` Paul Durrant
@ 2009-11-09 10:15       ` James Harper
  0 siblings, 0 replies; 6+ messages in thread
From: James Harper @ 2009-11-09 10:15 UTC (permalink / raw)
  To: Paul Durrant; +Cc: xen-devel

> 
> James Harper wrote:
> >
> > No PnP. I/O was being saturated though - I was performing a restore
via
> > network to the disk on the machine that crashed.
> >
> > Using phy: or file: I can restore 600GB with no problems at all.
With
> > tap:aio it crashes after a few tens of GB.
> >
> 
> Another guess then... tap will probably have more outstanding
> transactions than back as its datapath is likely to be longer and so
is
> higher latency. Is your frontend overflowing a queue of outstanding
SRBs?
> 

Thanks, that's a good lead. I think Windows is pretty limiting in the
amount of outstanding I/O that it allows (16 outstanding requests?) but
maybe that is too much for tap... I'll double check that I am catering
for a ring-full condition.

James

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2009-11-09 10:15 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-07 22:51 BSoD with GPLPV + tap:aio James Harper
2009-11-07 22:54 ` James Harper
2009-11-09 10:04 ` Paul Durrant
2009-11-09 10:06   ` James Harper
2009-11-09 10:13     ` Paul Durrant
2009-11-09 10:15       ` James Harper

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.