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

[Xen-devel] Virtual Block Device: frame_and_sects in blkif_request_t

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Ivan Kelly" <ivanbkelly@xxxxxxxxx>
  • Date: Tue, 28 Mar 2006 16:55:58 +0100
  • Delivery-date: Tue, 28 Mar 2006 15:57:29 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=qOuRgIlxBXsuI2rAA/zs45ubmqk+JmgSSPGi5g7UodsUJgV3CLxTeOiRw9clz4D7RxcfUpNcwpPNzsXSRw+2K6dtEpQf5HpxstmykL+UlEoaMpDblnXmIgGZ8h4ZnzzZVz8LK5gdCxdapr9vnxy/xm+7jW8ihS1guM/Clsjy2b4=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Could someone explain the frame_and_sects field of blkif_request_t(on
2.0.7) for me. From what I make out from the bsd and linux drivers,
these entries specify a machine frame and the section of the machine
frame to write from/copy to. Where I'm confused is the definition of
the size of these sections. Are they each 512 bytes in size?
Then there is the sector_number field. Are all requests written within
this sector, with the second entry in frames_and_sects being written
directly after the first entry which is written at the very start of
the segment, etc?
Ivan Kelly

Xen-devel mailing list



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