Xen network TODO

From Xen

Jump to: navigation, search

This is a list of open work items for Xen network project.

These items are mostly Linux specific. If you need help developing for other OSes, don't hesitate to email Xen-devel with your questions.

Contents

In progress

New baseline for Xen network

  • split event channels (done)
  • kthread + NAPI 1:1 model (done)

After switching to new baseline, you can get better scheduling fairness among vifs, mitigate interrupts to some extend, and have better aggregated throughput.

But please also note that you would need irqbalance to run in Dom0 (or your backend driver domain), otherwise you might get worse performance than before.

Unfortunately most in stock irqbalance would not work in Dom0 as it doesn't classify xen-dyn-event properly, you would need compile from the latest irqbalance master branch.

Open Work Items

Multipage ring
Contact: xen-devel@lists.xen.org
Description: The max outstanding amount of data the it can have is 898kB (64K of data use 18 slot, out of 256. 256 / 18 = 14, 14 * 64KB). This can be expanded by having multi-page to expand the ring. This would benefit NFS and bulk data transfer (such as netperf data).
References: Not specified, useful references.
Multiqueue support
Contact: xen-devel@lists.xen.org
Description: create many TX and RX rings for vif, scales better when DomU has more vcpus.
References: Not specified, useful references.
Don't gnt_copy all of the requests
Contact: xen-devel@lists.xen.org
Description: Instead don't touch them and let the Xen IOMMU create appropriate entries. This would require the DMA API in dom0 to be aware whether the grant has been done and if not (so FOREIGN, aka no m2p_override), then do the hypercall to tell the hypervisor that this grant is going to be used by a specific PCI device. This would create the IOMMU entry in Xen.
References: Not specified, useful references.
Do persistent mapping on guest TX side
Contact: xen-devel@lists.xen.org
Description: This would only be done from frontend -> backend path. However we could exhaust initial domains memory.
References: Not specified, useful references.
Affinity of the frontend and backend being on the same NUMA node
Contact: xen-devel@lists.xen.org
Description: This touches upon the discussion about NUMA and having PV guests be aware of memory layout. It also means that each backend kthread needs to be on a different NUMA node.
References: Not specified, useful references.
Personal tools