From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Ray Kinsella <mdr@ashroe.eu>, xuan.ding@intel.com
Cc: thomas@monjalon.net, stephen@networkplumber.org,
mb@smartsharesystems.com, dev@dpdk.org
Subject: Re: [PATCH] doc: announce header split deprecation
Date: Tue, 12 Jul 2022 14:43:03 +0300 [thread overview]
Message-ID: <824ea4bc-38ba-06f0-95ad-19d3dbd10e2e@oktetlabs.ru> (raw)
In-Reply-To: <87mtf7yo2l.fsf@mdr78.vserver.site>
On 5/24/22 17:58, Ray Kinsella wrote:
>
> xuan.ding@intel.com writes:
>
>> 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>
>
>
> Acked-by: Ray Kinsella <mdr@ashroe.eu>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
next prev parent reply other threads:[~2022-07-12 11:43 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 [this message]
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 ` [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=824ea4bc-38ba-06f0-95ad-19d3dbd10e2e@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=mdr@ashroe.eu \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--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).