From: Zhe Tao <zhe.tao@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2] i40e: configure the vector PMD option as no for default for l3fwd undefined ptype issue
Date: Tue, 24 Nov 2015 02:47:11 +0800 [thread overview]
Message-ID: <1448304431-26448-1-git-send-email-zhe.tao@intel.com> (raw)
In-Reply-To: <1447778782-8659-1-git-send-email-zhe.tao@intel.com>
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 <zhe.tao@intel.com>
---
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
next prev parent reply other threads:[~2015-11-23 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 16:46 [dpdk-dev] [PATCH] " Zhe Tao
2015-11-18 5:30 ` Zhang, Helin
2015-11-23 11:11 ` Thomas Monjalon
2015-11-23 18:47 ` Zhe Tao [this message]
2015-11-23 22:07 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1448304431-26448-1-git-send-email-zhe.tao@intel.com \
--to=zhe.tao@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).