From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id B1F10231C for ; Mon, 23 Nov 2015 19:47:40 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga103.jf.intel.com with ESMTP; 23 Nov 2015 10:47:17 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,338,1444719600"; d="scan'208";a="1136633" Received: from shvmail01.sh.intel.com ([10.239.29.42]) by fmsmga004.fm.intel.com with ESMTP; 23 Nov 2015 10:47:17 -0800 Received: from shecgisg004.sh.intel.com (shecgisg004.sh.intel.com [10.239.29.89]) by shvmail01.sh.intel.com with ESMTP id tANIlFTG025318; Tue, 24 Nov 2015 02:47:15 +0800 Received: from shecgisg004.sh.intel.com (localhost [127.0.0.1]) by shecgisg004.sh.intel.com (8.13.6/8.13.6/SuSE Linux 0.8) with ESMTP id tANIlDMp026484; Tue, 24 Nov 2015 02:47:15 +0800 Received: (from zhetao@localhost) by shecgisg004.sh.intel.com (8.13.6/8.13.6/Submit) id tANIlDmr026480; Tue, 24 Nov 2015 02:47:13 +0800 From: Zhe Tao To: dev@dpdk.org Date: Tue, 24 Nov 2015 02:47:11 +0800 Message-Id: <1448304431-26448-1-git-send-email-zhe.tao@intel.com> X-Mailer: git-send-email 1.7.4.1 In-Reply-To: <1447778782-8659-1-git-send-email-zhe.tao@intel.com> References: <1447778782-8659-1-git-send-email-zhe.tao@intel.com> Subject: [dpdk-dev] [PATCH v2] i40e: configure the vector PMD option as no for default for l3fwd undefined ptype issue X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2015 18:47:41 -0000 PATCH v1: configure the vector PMD option as no for FVL PATCH v2: Update the "know issues" for 2.2 release note Issue: l3fwd app need the ptype in the mbuf to forwarding 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 --- config/common_bsdapp | 2 +- config/common_linuxapp | 2 +- doc/guides/rel_notes/release_2_2.rst | 6 +++++- 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/config/common_bsdapp b/config/common_bsdapp index 7df0763..a9b51ff 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 52173d5..56d6287 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 0781ae6..0fe4cbb 100644 --- a/doc/guides/rel_notes/release_2_2.rst +++ b/doc/guides/rel_notes/release_2_2.rst @@ -215,7 +215,11 @@ Other Known Issues ------------ - +* l3fwd app now cannot handle the receive packets properly without ptype. + When using the FVL PMD for l3fwd, need to make sure the receive packets + will have the ptype set, but now the FVL vPMD does not support ptype, + so please configure the vPMD option as no when using the l3fwd on FVL. + API Changes ----------- -- 2.1.4