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

Re: [Xen-devel] Network questions

To: "Xiaofang Chen" <xiachen@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Network questions
From: Mark Williamson <Mark.Williamson@xxxxxxxxxxxx>
Date: Tue, 29 Jun 2004 19:27:06 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Mark.Williamson@xxxxxxxxxxxx
Delivery-date: Tue, 29 Jun 2004 21:11:06 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Message from "Xiaofang Chen" <xiachen@xxxxxxxxxxx> of "Mon, 28 Jun 2004 21:50:54 MDT." <00e001c45d8c$47db3750$7eb6639b@XFCHEN>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Are you using Xen 1.2 or unstable?  There have been big changes to networking 
in the unstable tree.  In my previous e-mail I was describing the current 
state of the unstable tree.

The old IO world: (as used by Xen 1.2 and as described in the SOSP paper)
* Device drivers for physical network devices are in Xen.
* All domains (including 0) use a "virtual" network driver, which talks to 
Xen.  Xen then routes packets between domains or out onto the physical network.
* VIRQ_NET is the IRQ associated with a virtual network device.  Xen uses it 
to signal a domain when it has been sent data by another domain or from the 
physical network.
* There's no "backend", just Xen.

The new IO world: (as used by the Unstable tree and the forthcoming 2.0 
release)
* Xen does not contain device drivers anymore.
* Instead, the device drivers for physical devices run in domains.  Usually, 
all the drivers for your hardware run in dom0.
* A domain that's controlling physical devices can export virtual devices to 
other domains.  The driver which exports a device to other domains is called 
the "backend".
* The driver which imports a virtual device from the backend is called the 
"frontend".  This driver runs in unprivileged domains to give them their 
virtual devices.  It's a lot like the old (1.2) virtual network interface 
driver except that it talks to another domain instead of to Xen.
* VIRQ_NET does not exist anymore.  Instead, the backend driver (in the domain 
that controls the hardware) can send an interrupt to the frontend driver (in 
the domain using the virtual devices) using the event channel mechanism I 
described in my last e-mail.

Does that make sense?

Mark



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>