[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] block ring interface: nr_segments = 0 results in BLKIF_RSP_ERROR


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Chris Youb <chris_youb@xxxxxxxx>
  • Date: Thu, 24 Aug 2006 16:41:36 -0400 (EDT)
  • Delivery-date: Thu, 24 Aug 2006 13:42:05 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=P5feZo4jcf1ls2gsvpEqeUmeeoYYQm9SOpYxvzSm/XiuJT8IToAEdHxzPVw9THJd9n42jnkCxHVAPD+FNJ4hhbSShxpufORz7mcnTdv9nJT/V7qdxYuZHxDYMM6PTiBrsi+tzl2yRefczv6/F02k3o6wPodajt+lBu2ERAIlNss= ;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I am currently developing a blkfront.c for a custom OS over Xen 3.0.2-2.  Typical I/O is working, however, I ran into an error while testing a corner case.
 
On standard I/O, where  { 1 <= nr_segments < BLKIF_MAX_SEGMENTS_PER_REQUEST } blkif_int()'s bret->status returns BLKIF_RSP_OKAY.
 
Yet when { nr_segments == 0 } blkif_int's bret->status is non-zero. (Yes I realize this is an I/O call of zero-length.)
 
I checked the documentation and section "8.2.2 Block ring interface" states the following but doesn't exclude 0:
 
"nr_segments
     number of segments for scatter / gather IO described by this request"
 
1) Is it possible there is a problem w/ my front-end driver (ie does anyone else see this behaviour)?
 
2) If this is back-end related, shouldn't it just return BLKIF_RSP_OKAY?


Now you can have a huge leap forward in email: get the new Yahoo! Mail.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.