From: Zhe Tao Date: Mon, 23 Nov 2015 18:47:11 +0000 (+0800) Subject: config: disable i40e vector driver X-Git-Tag: spdx-start~8012 X-Git-Url: http://git.droids-corp.org/?a=commitdiff_plain;h=850d6bb7d584cbbdbc06b0e93fc5c53b6ea44791;p=dpdk.git config: disable i40e vector driver Issue: l3fwd app need the ptype in the mbuf to forward the packets properly. But now some drivers like virtio driver and FVL vPMD will not set the ptype in mbuf, so l3fwd cannot work properly on that kind of drivers. Configure the vector PMD option as no for default as a work around for l3fwd. After the l3fwd app can handle the undefined ptype or the i40e vPMD can return the ptype, the option will be set as yes for default again. Signed-off-by: Zhe Tao Acked-by: Helin Zhang --- diff --git a/config/common_bsdapp b/config/common_bsdapp index ae7374a416..bdf1fcd15f 100644 --- a/config/common_bsdapp +++ b/config/common_bsdapp @@ -189,7 +189,7 @@ CONFIG_RTE_LIBRTE_I40E_DEBUG_TX=n CONFIG_RTE_LIBRTE_I40E_DEBUG_TX_FREE=n CONFIG_RTE_LIBRTE_I40E_DEBUG_DRIVER=n CONFIG_RTE_LIBRTE_I40E_RX_ALLOW_BULK_ALLOC=y -CONFIG_RTE_LIBRTE_I40E_INC_VECTOR=y +CONFIG_RTE_LIBRTE_I40E_INC_VECTOR=n CONFIG_RTE_LIBRTE_I40E_RX_OLFLAGS_ENABLE=y CONFIG_RTE_LIBRTE_I40E_16BYTE_RX_DESC=n CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_PF=64 diff --git a/config/common_linuxapp b/config/common_linuxapp index 0954eef40c..f72c46d7df 100644 --- a/config/common_linuxapp +++ b/config/common_linuxapp @@ -187,7 +187,7 @@ CONFIG_RTE_LIBRTE_I40E_DEBUG_TX=n CONFIG_RTE_LIBRTE_I40E_DEBUG_TX_FREE=n CONFIG_RTE_LIBRTE_I40E_DEBUG_DRIVER=n CONFIG_RTE_LIBRTE_I40E_RX_ALLOW_BULK_ALLOC=y -CONFIG_RTE_LIBRTE_I40E_INC_VECTOR=y +CONFIG_RTE_LIBRTE_I40E_INC_VECTOR=n CONFIG_RTE_LIBRTE_I40E_RX_OLFLAGS_ENABLE=y CONFIG_RTE_LIBRTE_I40E_16BYTE_RX_DESC=n CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_PF=64 diff --git a/doc/guides/rel_notes/release_2_2.rst b/doc/guides/rel_notes/release_2_2.rst index 4fea43329d..8c7776823f 100644 --- a/doc/guides/rel_notes/release_2_2.rst +++ b/doc/guides/rel_notes/release_2_2.rst @@ -228,6 +228,10 @@ Other Known Issues ------------ +* Some drivers do not fill the packet type when receiving. + As the l3fwd example application requires this info, the i40e vector + driver must be disabled to benefit of the packet type with i40e. + API Changes -----------