Patrick Fu <patrick...@intel.com> wrote: > Network Test Access Point (TAP) is the network monitoring service > commonly adotpted in SDN-based network infrastructures. When VMs are > inter-connected over virtual switches, TAP requires vSwitch to mirror > out network traffics from specific workload VM ports to the TAP > device/VM ports. Classical mirroring impmentations in vSwitch make an > extra copy of the source packets, which results in significant degradation > in the throughput levels vSwitch could normally archieve. Therefore, we > propose a new set of APIs to support high-throughput packet mirroring > through hardware offloading.
In the RFC thread, you mentioned you were targetting vhost where there is no hardware offload. If it targets hardware offload, it should be in rte_flow. Even if no device offload, we could implement it in rte_flow. If you think it does not fit with rte_flow because it is forwarding traffic between devices, then I think rte_graph or rte_pipeline may fit. In general I am against adding a library restricted to some specific forwarding use cases.
