net/tap: add remote netdevice traffic capture
authorPascal Mazon <pascal.mazon@6wind.com>
Thu, 23 Mar 2017 08:42:11 +0000 (09:42 +0100)
committerFerruh Yigit <ferruh.yigit@intel.com>
Tue, 4 Apr 2017 16:59:47 +0000 (18:59 +0200)
commit2bc06869cd94195e986cfb7939a549d7050097e8
tree050bf364807b39d64f5364fc4cd8230a853f9a89
parent0781f5762cfe0a7bbada05da4380f2efecfe79ff
net/tap: add remote netdevice traffic capture

By default, a tap netdevice is of no use when not fed by a separate
process. The ability to automatically feed it from another netdevice
allows applications to capture any kind of traffic normally destined to
the kernel stack.

This patch implements this ability through a new optional "remote"
parameter.

Packets matching filtering rules created with the flow API are matched
on the remote device and redirected to the tap PMD, where the relevant
action will be performed.

Signed-off-by: Pascal Mazon <pascal.mazon@6wind.com>
Acked-by: Olga Shern <olgas@mellanox.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
doc/guides/nics/tap.rst
drivers/net/tap/rte_eth_tap.c
drivers/net/tap/rte_eth_tap.h
drivers/net/tap/tap_flow.c
drivers/net/tap/tap_flow.h