dpdk: quad loop dpdk tx and code optimizations 78/3878/12
authorDamjan Marion <damarion@cisco.com>
Tue, 15 Nov 2016 11:50:28 +0000 (12:50 +0100)
committerDave Barach <openvpp@barachs.net>
Tue, 22 Nov 2016 22:11:12 +0000 (22:11 +0000)
commit22766b824d5b243c7353df0d80e73a50aa9f73ff
tree2fa04fff2e06c498bafa72d92ecb3a02ed876b2c
parent177bbdcd8fa4e7621c5bdd3afd8c6e74b603e096
dpdk: quad loop dpdk tx and code optimizations

Beside performance optimization this change
also introduces rte_mbuf validation in dpdk tx code.
If packet is arrving from non-DPDK source like
self-originated packets or non-dpdk devices (tuntap,
af_packet, netmap, pg) it is not anymore exepcted
that it contains valid rte_mbuf metadata unless it is
explictely stated by setting VNET_BUFFER_RTE_MBUF_VALID
flag.

dpdk-input node sets VNET_BUFFER_RTE_MBUF_VALID on all
packets and that reduces cost of validation in tx node.

Change-Id: I4ad40f398f7b5cf90656a2069a27c0f6fc13efba
Signed-off-by: Damjan Marion <damarion@cisco.com>
vnet/vnet/buffer.h
vnet/vnet/devices/dpdk/device.c
vnet/vnet/devices/dpdk/init.c
vnet/vnet/ipsec/esp_encrypt.c