From: Qi Zhang <qi.z.zhang@intel.com>
To: ferruh.yigit@intel.com
Cc: dev@dpdk.org, Qi Zhang <qi.z.zhang@intel.com>
Subject: [dpdk-dev] [PATCH 2/2] doc/fm10k: convert to new offload API
Date: Wed, 23 May 2018 10:56:07 +0800 [thread overview]
Message-ID: <20180523025607.47980-2-qi.z.zhang@intel.com> (raw)
In-Reply-To: <20180523025607.47980-1-qi.z.zhang@intel.com>
Cleanup document to convert old rxmode and txq_flags to new offload
bit mask.
Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
---
doc/guides/nics/fm10k.rst | 27 ++++++++-------------------
1 file changed, 8 insertions(+), 19 deletions(-)
diff --git a/doc/guides/nics/fm10k.rst b/doc/guides/nics/fm10k.rst
index c44e226e3..d1391e997 100644
--- a/doc/guides/nics/fm10k.rst
+++ b/doc/guides/nics/fm10k.rst
@@ -79,14 +79,14 @@ Other features are supported using optional MACRO configuration. They include:
To enable via ``RX_OLFLAGS`` use ``RTE_LIBRTE_FM10K_RX_OLFLAGS_ENABLE=y``.
-To guarantee the constraint, the following configuration flags in ``dev_conf.rxmode``
+To guarantee the constraint, the following capabilities in ``dev_conf.rxmode.offloads``
will be checked:
-* ``hw_vlan_extend``
+* ``DEV_RX_OFFLOAD_VLAN_EXTEND``
-* ``hw_ip_checksum``
+* ``DEV_RX_OFFLOAD_CHECKSUM``
-* ``header_split``
+* ``DEV_RX_OFFLOAD_HEADER_SPLIT``
* ``fdir_conf->mode``
@@ -106,19 +106,9 @@ TX Constraint
Features not Supported by TX Vector PMD
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-TX vPMD only works when ``txq_flags`` is set to ``FM10K_SIMPLE_TX_FLAG``.
-This means that it does not support TX multi-segment, VLAN offload or TX csum
-offload. The following MACROs are used for these three features:
+TX vPMD only works when offloads is set to 0
-* ``ETH_TXQ_FLAGS_NOMULTSEGS``
-
-* ``ETH_TXQ_FLAGS_NOVLANOFFL``
-
-* ``ETH_TXQ_FLAGS_NOXSUMSCTP``
-
-* ``ETH_TXQ_FLAGS_NOXSUMUDP``
-
-* ``ETH_TXQ_FLAGS_NOXSUMTCP``
+This means that it does not support any TX offload.
Limitations
-----------
@@ -149,9 +139,8 @@ CRC striping
~~~~~~~~~~~~
The FM10000 family of NICs strip the CRC for every packets coming into the
-host interface. So, CRC will be stripped even when the
-``rxmode.hw_strip_crc`` member is set to 0 in ``struct rte_eth_conf``.
-
+host interface. So, CRC will be stripped even when ``DEV_RX_OFFLOAD_CRC_STRIP``
+in ``rxmode.offloads`` is NOT set in ``struct rte_eth_conf``.
Maximum packet length
~~~~~~~~~~~~~~~~~~~~~
--
2.13.6
next prev parent reply other threads:[~2018-05-23 2:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 2:56 [dpdk-dev] [PATCH 1/2] doc/ixgbe: " Qi Zhang
2018-05-23 2:56 ` Qi Zhang [this message]
2018-05-24 14:20 ` Ferruh Yigit
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=20180523025607.47980-2-qi.z.zhang@intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).