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

[Xen-devel] network flow of control


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Diwaker Gupta <diwakergupta@xxxxxxxxx>
  • Date: Thu, 30 Jun 2005 15:04:02 -0700
  • Delivery-date: Thu, 30 Jun 2005 22:02:55 +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=d/N6yeP6gMZLR9omxnUnCRtfS0m7jb3L99KTj1KFs9+KyV67FD9AMrgjukM2hldsfLOBe7axhYzVLaW652m2ibG5JZN5Ln7cXJI6uAa0mxCi9WgG6OkSuU3krKVOwsna2PtwyT/Zbh1I89Cclat0ARVCFVami1yp+CRM2pFj/j0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi everyone,

I'm just trying to get a little more understanding on the networking
flow control in Xen. Is there any documentation on how everything is
glued together -- things like where exactly is the code that connects
a network frontend to a network backend, for example;

I've got some idea from docs/misc/blkif-drivers-explained.txt, and of
course the re-structuring I/O paper.

Thanks,
Diwaker
-- 
Diwaker Gupta
http://resolute.ucsd.edu/diwaker

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