From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Helin Zhang <helin.zhang@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 1/3] ixgbe: fix offload config option name
Date: Fri, 31 Jul 2015 23:11:28 +0200 [thread overview]
Message-ID: <1438377090-22232-2-git-send-email-thomas.monjalon@6wind.com> (raw)
In-Reply-To: <1438377090-22232-1-git-send-email-thomas.monjalon@6wind.com>
The RX_OLFLAGS option was renamed from DISABLE to ENABLE in driver code
and linux config.
It is now renamed also in bsd config and documentation.
Fixes: 359f106a69a9 ("ixgbe: prefer enabling olflags rather than not disabling")
Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
config/common_bsdapp | 2 +-
doc/guides/nics/ixgbe.rst | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/config/common_bsdapp b/config/common_bsdapp
index 2c6eb40..650de38 100644
--- a/config/common_bsdapp
+++ b/config/common_bsdapp
@@ -174,7 +174,7 @@ CONFIG_RTE_LIBRTE_IXGBE_DEBUG_TX_FREE=n
CONFIG_RTE_LIBRTE_IXGBE_DEBUG_DRIVER=n
CONFIG_RTE_LIBRTE_IXGBE_PF_DISABLE_STRIP_CRC=n
CONFIG_RTE_IXGBE_INC_VECTOR=n
-CONFIG_RTE_IXGBE_RX_OLFLAGS_DISABLE=n
+CONFIG_RTE_IXGBE_RX_OLFLAGS_ENABLE=y
#
# Compile burst-oriented I40E PMD driver
diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst
index 62cc0aa..8cae299 100644
--- a/doc/guides/nics/ixgbe.rst
+++ b/doc/guides/nics/ixgbe.rst
@@ -95,7 +95,7 @@ Other features are supported using optional MACRO configuration. They include:
* HW extend dual VLAN
-* Enabled by RX_OLFLAGS (RTE_IXGBE_RX_OLFLAGS_DISABLE=n)
+* Enabled by RX_OLFLAGS (RTE_IXGBE_RX_OLFLAGS_ENABLE=y)
To guarantee the constraint, configuration flags in dev_conf.rxmode will be checked:
@@ -154,13 +154,13 @@ Sample Application Notes
testpmd
^^^^^^^
-By default, using CONFIG_RTE_IXGBE_RX_OLFLAGS_DISABLE=n:
+By default, using CONFIG_RTE_IXGBE_RX_OLFLAGS_ENABLE=y:
.. code-block:: console
./x86_64-native-linuxapp-gcc/app/testpmd -c 300 -n 4 -- -i --burst=32 --rxfreet=32 --mbcache=250 --txpt=32 --rxht=8 --rxwt=0 --txfreet=32 --txrst=32 --txqflags=0xf01
-When CONFIG_RTE_IXGBE_RX_OLFLAGS_DISABLE=y, better performance can be achieved:
+When CONFIG_RTE_IXGBE_RX_OLFLAGS_ENABLE=n, better performance can be achieved:
.. code-block:: console
--
2.4.2
next prev parent reply other threads:[~2015-07-31 21:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 15:08 [dpdk-dev] config files maintenance Thomas Monjalon
2015-07-31 15:29 ` Zhang, Helin
2015-07-31 15:31 ` Thomas Monjalon
2015-07-31 15:39 ` Zhang, Helin
2015-07-31 15:43 ` Thomas Monjalon
2015-07-31 16:34 ` Zhang, Helin
2015-07-31 15:41 ` Ananyev, Konstantin
2015-07-31 20:45 ` Thomas Monjalon
2015-07-31 21:11 ` [dpdk-dev] [PATCH 0/3] sync linux/bsd config options Thomas Monjalon
2015-07-31 21:11 ` Thomas Monjalon [this message]
2015-07-31 21:11 ` [dpdk-dev] [PATCH 2/3] config: enable same drivers options for linux and bsd Thomas Monjalon
2015-07-31 21:11 ` [dpdk-dev] [PATCH 3/3] config: remove kni options for bsd Thomas Monjalon
2015-07-31 21:24 ` Zhang, Helin
2015-08-03 10:44 ` [dpdk-dev] [PATCH 0/3] sync linux/bsd config options 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=1438377090-22232-2-git-send-email-thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=konstantin.ananyev@intel.com \
/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).