WARNING - OLD ARCHIVES

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

xen-devel

[Xen-devel] understanding network split device drivers

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] understanding network split device drivers
From: Diwaker Gupta <diwaker.lists@xxxxxxxxx>
Date: Tue, 6 Sep 2005 17:06:45 -0700
Delivery-date: Wed, 07 Sep 2005 00:04:40 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=PWoHXoRKNX1aYfIaB5yTQASZqlg+zQrmwIe8wmTIeULOxMjCCLEBO11bLHT32BeCmumIm9eTjbPNI6g/B8XSjayi6rT0iGS0qA4iquAewcv2PaAaYqs4zIFT2izHTSVTfGl2NR/olvBgGsteU9Qot9yWr97Mw0Zif439/QXZJpI=
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: diwaker.lists@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I'm trying to understand the architecture for I/O devices (in particular, the
network drivers) in Xen. I know the broad design and structure of the split
devices drivers. The following picture will hopefully make it easier for
people to answer my questions:

                dom-0                          dom-1
------------------------------------     --------------
    device driver        backend   |     |   frontend
                   ==>             | ==> |
    (eg: e1000)       (eg: netback)|     |(eg: netfront)
------------------------------------     --------------
                  ||                  
                  \/                  
             (questions!!)


I'm not very knowledgeable on the linux networking stack, so bear with me if I
ask something obvious.

o where and how is this pipelining (between the actual device driver and the
backend) set up in the code? 

o is it something xen specific, or is it done via standard linux networking? 

o is there some buffer/queue between the backend and the actual device driver? 

o does the backend get any kind of notification from the hardware in case the
send/recv fails (since IIUC netback queues requests asynchronous processing)

o where exactly do the bridge utils fit in this picture?

TIA
Diwaker
-- 
Web/Blog/Gallery: http://floatingsun.net

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] understanding network split device drivers, Diwaker Gupta <=