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

[Xen-devel] Re: questions about the block backend/frontend driver


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Yuming fang" <fangyuming.leo@xxxxxxxxx>
  • Date: Tue, 9 Sep 2008 20:43:07 +0800
  • Delivery-date: Tue, 09 Sep 2008 05:43:31 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=te56sawozirZTwX+C9PYJUngEuQD1kfLkjW14BgOdePHnyTJ0Oyr+mXrFu78IuiOCN mLtzyVDO1+J819HzMJIpXjWjRKA9T0HFgPHa6huOMGY7aazq5mDUER0jXg8oB2y062X4 xifP5Md8lW9C3I8APPcBUiXca0ttnwaBeXi3E=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

 
Nobody answer these questions? I want to know if I could implement the I/O disk scheduling in Xen and then I could not modify the corresponding code(I/O Scheduling algorithms) of Linux Kernel?
 
Yuming

2008/9/8 Yuming fang <fangyuming.leo@xxxxxxxxx>
Hi, Everyone,
 
I am trying to understand the code of the block backend/frontend driver. I konw the blkback and blkfront communicate with each other through event channel and buffer ring. But there are some questions I could not understand.
 
1. When dom0 receive one disk request from domU1 and another disk request from domU2 simultaneously, how these two disk requests are pushed into Linux Kernel I/O Scheduler? How the Xen sort them before pushing them into the Linux Kernel I/O Scheduler?
 
2. Is there a disk request queue in the Xen to hold these disk requests, so that the Xen could only push the disk requests in the queue into the linux kernel I/O Scheduler?
 
I would appreciate it very much if anyone could give me some help.
 
Yuming
 

_______________________________________________
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®.