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

[Xen-users] Packet flow in Xen

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Siddharth Wagh <swagh@xxxxxxxxxxxxxxxx>
  • Date: Tue, 23 Nov 2010 08:55:27 -0500
  • Delivery-date: Tue, 23 Nov 2010 05:58:01 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=kWtNwgozGLZUDqI75dFuScsO/m9vlOEmIucP2FlLzZ+aOj967TR+wOJ8+cPZa5RxGQ 865NLBTvByfHVE3Hkw12ILIVyZew/f20HyV44pEPATRAK0ENJKSiE3Xn332cQDn/ZOQi lGMGhIaQOBkn0KEP9P5GhRRkUmNZBe45C9k+c=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello all,

I am trying to understand the underlying mechanism behind how exactly the packet flows in a Xen virtualized system. There are some gaps in my knowledge that need to be filled.

Guest --> Internet:
1. Guest writes request on I/O ring buffers in hypervisor (using netfront.c)
2. Guest writes notification in grant tables in XenStore using event channels.
3. Dom-0 reads grant reference and locates/reads request from ring buffer (using netback.c)
4. Packet is bridged using Xenbr0 (created by network-bridge & vif-bridge to pass through peth0 (ebtables module).
5. There is interaction between real device driver in Dom-0 and NIC and packet is probably sent from ring buffers on the Internet using DMA.

I know there are lot of loopholes here, and I would really appreciate if someone could help me grasp the exact scenario, especially referring to scripts that carry out the process.

Thanks & Regards,
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.