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/
Home Products Support Community News


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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] questions about the block backend/frontend driver
From: "Yuming fang" <fangyuming.leo@xxxxxxxxx>
Date: Mon, 8 Sep 2008 15:05:04 +0800
Delivery-date: Mon, 08 Sep 2008 00:05:32 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=8lp6C4KiM/Fh1DbNgihVmrbyKhjtHhcbT2/+r+YLUuE=; b=ms0ljConcasV9bUSQg6nuQM6t0nlrzC9YQkMiBlqrQBhamiJ9qETZ8bxkA12oOYDPR 6yJSWAtnH/HeKiG8gW8akbn58p14JvY4bzxk+PQPZXWPQZfI6JKz9i5vX++TNl+h5fy0 Z19ylvjHL8Bjb26RmED3bg7FsF21tdFmpHHYQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=R7zTYCpWBg55RZlROIM7pyHIdoEu0Jyml8xxv/s8LKd3ShLtYlDJA0sNfUdi9DHrAu jfdf04dCuKlrnx9q/2Hq4fNRdI6cWMrKr/6ygsZ8ATDt8JUbRf/JDw1llNvwG3WOxqhv hkalRzW6NVYmEmq0EwG5HrIF+VvOxVB3OFDHQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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.
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>