DPDK patches and discussions
 help / color / mirror / Atom feed
From: xuan.ding@intel.com
To: thomas@monjalon.net, mdr@ashroe.eu,
	andrew.rybchenko@oktetlabs.ru, ferruh.yigit@xilinx.com,
	viacheslavo@nvidia.com
Cc: dev@dpdk.org, stephen@networkplumber.org,
	mb@smartsharesystems.com, qi.z.zhang@intel.com,
	asekhar@marvell.com, pbhagavatula@marvell.com,
	Xuan Ding <xuan.ding@intel.com>
Subject: [PATCH v2] doc: announce header split deprecation
Date: Fri, 15 Jul 2022 20:30:55 +0000	[thread overview]
Message-ID: <20220715203055.64074-1-xuan.ding@intel.com> (raw)
In-Reply-To: <20220523142016.44451-1-xuan.ding@intel.com>

From: Xuan Ding <xuan.ding@intel.com>

RTE_ETH_RX_OFFLOAD_HEADER_SPLIT offload was introduced some time ago to
substitute bit-field header_split in struct rte_eth_rxmode. It allows
to enable per-port header split offload with the header size controlled
using split_hdr_size in the same structure.

Right now, no single PMD actually supports RTE_ETH_RX_OFFLOAD_HEADER_SPLIT
with above definition. Many examples and test apps initialize the field
to 0 explicitly. The most of drivers simply ignore split_hdr_size since
the offload is not advertised, but some double-check that its value is 0.

So the RTE_ETH_RX_OFFLOAD_HEADER_SPLIT and split_header_size field
will be removed in DPDK 22.11. After DPDK 22.11 LTS, the
RTE_ETH_RX_OFFLOAD_BUFFER_SPLIT can still be used for per-queue Rx
packet split offload, which is configured by rte_eth_rxseg_split.

Signed-off-by: Xuan Ding <xuan.ding@intel.com>
Acked-by: Ray Kinsella <mdr@ashroe.eu>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Acked-by: Ferruh Yigit <ferruh.yigit@xilinx.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
---
v2:
* Refine doc to mention remained RTE_ETH_RX_OFFLOAD_BUFFER_SPLIT.
---
 doc/guides/rel_notes/deprecation.rst | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 1e5e532e60..ae37559275 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -158,3 +158,10 @@ Deprecation Notices
   applications should be updated to use the ``dmadev`` library instead,
   with the underlying HW-functionality being provided by the ``ioat`` or
   ``idxd`` dma drivers
+
+* ethdev: Since no single PMD supports ``RTE_ETH_RX_OFFLOAD_HEADER_SPLIT`` offload
+and the ``split_hdr_size`` field in structure ``rte_eth_rxmode`` to enable per-port
+header split as they were designed, they will be removed in DPDK 22.11.
+After DPDK 22.11 LTS, the ``RTE_ETH_RX_OFFLOAD_BUFFER_SPLIT`` can still be
+used for per-queue Rx packet split offload, and it is configured
+by ``rte_eth_rxseg_split``.
-- 
2.17.1


  parent reply	other threads:[~2022-07-15 20:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 14:20 [PATCH] " xuan.ding
2022-05-24 14:58 ` Ray Kinsella
2022-07-12 11:43   ` Andrew Rybchenko
2022-07-13  9:49 ` Thomas Monjalon
2022-07-14  5:50   ` Ding, Xuan
2022-07-14  8:08     ` Thomas Monjalon
2022-07-14 12:54       ` Ding, Xuan
2022-07-14 13:25         ` Thomas Monjalon
2022-07-14 14:07           ` Ding, Xuan
2022-07-14 15:58             ` Ferruh Yigit
2022-07-14 16:03               ` Ferruh Yigit
2022-07-15  8:52                 ` Ding, Xuan
2022-07-14 16:56               ` Slava Ovsiienko
2022-07-15  8:28                 ` Ding, Xuan
2022-07-15 11:34                   ` Ferruh Yigit
2022-07-15 12:43                     ` Ding, Xuan
2022-07-15 12:13           ` Andrew Rybchenko
2022-07-15 12:44             ` Ding, Xuan
2022-07-15 20:30 ` xuan.ding [this message]
2022-07-16 21:28   ` [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=20220715203055.64074-1-xuan.ding@intel.com \
    --to=xuan.ding@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=asekhar@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=mb@smartsharesystems.com \
    --cc=mdr@ashroe.eu \
    --cc=pbhagavatula@marvell.com \
    --cc=qi.z.zhang@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.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).