DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: xuan.ding@intel.com
Cc: andrew.rybchenko@oktetlabs.ru, mdr@ashroe.eu, dev@dpdk.org,
	stephen@networkplumber.org, mb@smartsharesystems.com,
	dev@dpdk.org
Subject: Re: [PATCH] doc: announce header split deprecation
Date: Wed, 13 Jul 2022 11:49:51 +0200	[thread overview]
Message-ID: <11233520.IZOipudI63@thomas> (raw)
In-Reply-To: <20220523142016.44451-1-xuan.ding@intel.com>

23/05/2022 16:20, 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 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.
> 
> Signed-off-by: Xuan Ding <xuan.ding@intel.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 4e5b23c53d..b8114f29ed 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -125,3 +125,7 @@ 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: After bit-field header split was removed, the ``RTE_ETH_RX_OFFLOAD_HEADER_SPLIT``
> +offload and the ``split_hdr_size`` field in structure ``rte_eth_rxmode`` to enable header
> +split offload are not supported in any PMDs. They will be removed in DPDK 22.11.

It would have been good to talk about rte_eth_rxseg_split
which is similar and configured per-queue.



  parent reply	other threads:[~2022-07-13  9:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 14:20 xuan.ding
2022-05-24 14:58 ` Ray Kinsella
2022-07-12 11:43   ` Andrew Rybchenko
2022-07-13  9:49 ` Thomas Monjalon [this message]
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 ` [PATCH v2] " xuan.ding
2022-07-16 21:28   ` 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=11233520.IZOipudI63@thomas \
    --to=thomas@monjalon.net \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=mdr@ashroe.eu \
    --cc=stephen@networkplumber.org \
    --cc=xuan.ding@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).