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] Netback & NetFront Driver

To: Xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Netback & NetFront Driver
From: TEJ <tejparkash.d@xxxxxxxxx>
Date: Sun, 8 Jul 2007 12:33:41 +0530
Delivery-date: Sun, 08 Jul 2007 00:01:40 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=BEi+0ADz9ihAYrFzK1tiCLKXOc5nzSmTpQ6cv9Nuu6xj/6A7yEMPMxxAJKLKxOzlhy4yWIxgi584hmgjMhrgRy2XcO3NMsw5YoWcUTMivnypngyzM7lRdWDl2ZbZbfDrWJv0flWu5wM3bKTwNcJ5Sxlo8BFZwJJ+5obW+TA1yRc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=b+Oxzf/wplx9O2A9n2Kt5WWD1mDDFzmpCQZHgtfT9CF/9iNWhpH1XZ18Kk74uFrYZs5UdxeAYihpoAY0Kw19uaY0JaiYXHoJykziWjGHM+XRHQ1SAc58sMmII475VFgWOgyFPkdltlBzfpqcI9+2TwnIeSinpgZpClY3mU/DtQ0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
hi

i am new to the xen development list. I am just curious about the
networking architecture of the XEN.

there are two separate things i have read.

first is the Network driver architecture is a spilt driver (Netfront
and NetBack)...
Second is while domu is coming up it creates the virtual interfaces
like (vif<id>.0 <--> (v)eth0).

I am unable to relate these two concept. As far as my understanding
say that, for all the (v)eth0, eth1, eth2 interface in domu is managed
by Netfront Driver. So IP layer in domu talks to Netfront Driver and
uses one of the veth and then pass packet through that channel i.e.
corresponding vif through hypervisor.

All the vif<id>.x interfaces in the dom0 will be managed by NetBack
Driver. Since all the vif's are grouped with bridge which actaully
forward the packet to the actual driver of correspinding vif
interface.

I just want somebody confirmation on that or somebody want to add
something over this will be helpful to me

i have attached one doc if some is interested can through some light on that..

i am sorry if it is totally a crap.

thanks
TEJ

Attachment: networking.doc
Description: MS-Word document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>