[Ksummit-2012-discuss] [ATTEND] zero copy networking, bridge vs macvtap, co-maintainership, pci
Michael S. Tsirkin
mst at redhat.com
Thu Jun 21 13:58:19 UTC 2012
I'd like to submit my name as someone who would like to attend the Kernel
Summit this year.
I'd like to discuss:
- zero copy networking
Driving a hardware device from userspace/VM let you use a NIC
without extra data copies, today, which might improve
throughput/CPU by about 10% in some setups, but what is the way
forward for setup that won't/can't dedicate a NIC to an app/VM?
Work is ongoing on tracking usage of specific pages in
net core, this addresses one of the requirements, but how to make
these setups safe against malicious apps/VMs?
What to do about tcp restransmits etc?
- Bridge versus macvtap
macvtap stated out without bridging features for setups such
as VEPA, which seemed to gain nothing from standard bridge
functionality, but seems to be gaining features such a bridging.
Is anything to be gained from integrating it back into bridge?
- co-maintainership issues. Being one of co-maintainers poses
some challenges on top of the usual ones for a maintainer.
Who picks up each patch? Is a patch acceptable to both maintainers?
etc. This is not at all unique though so I would like to learn
from others who maintain in a group: what works?
- PCI hotplug issues, this has already been covered in a previous
More information about the Ksummit-2012-discuss