From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: xuan.ding@intel.com, thomas@monjalon.net, viacheslavo@nvidia.com,
jerinj@marvell.com, cristian.dumitrescu@intel.com,
aman.deep.singh@intel.com, yuying.zhang@intel.com, chas3@att.com,
humin29@huawei.com, gakhil@marvell.com, qi.z.zhang@intel.com,
xiao.w.wang@intel.com, qiming.yang@intel.com,
wenjun1.wu@intel.com, mdr@ashroe.eu, ndabilpuram@marvell.com,
kirankumark@marvell.com, skori@marvell.com,
skoteshwar@marvell.com, grive@u256.net, beilei.xing@intel.com,
zr@semihalf.com, lironh@marvell.com, mczekaj@marvell.com,
nicolas.chautru@intel.com, orika@nvidia.com,
konstantin.v.ananyev@yandex.ru, radu.nicolau@intel.com,
roy.fan.zhang@intel.com, pbhagavatula@marvell.com,
bruce.richardson@intel.com, anatoly.burakov@intel.com,
jingjing.wu@intel.com, junfeng.guo@intel.com,
jasvinder.singh@intel.com, maxime.coquelin@redhat.com,
chenbo.xia@intel.com, Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2] ethdev: remove header split Rx offload
Date: Tue, 4 Oct 2022 12:21:21 +0300 [thread overview]
Message-ID: <b20ac171-2027-bede-92f8-06489b760768@oktetlabs.ru> (raw)
In-Reply-To: <a7678a3c-04c0-ece6-4df0-69a9b9983f00@oktetlabs.ru>
On 9/13/22 10:38, Andrew Rybchenko wrote:
> On 8/12/22 06:13, xuan.ding@intel.com wrote:
>> From: Xuan Ding <xuan.ding@intel.com>
>>
>> As announced in the deprecation note, this patch removes the Rx offload
>> flag 'RTE_ETH_RX_OFFLOAD_HEADER_SPLIT' and 'split_hdr_size' field from
>> the structure 'rte_eth_rxmode'. Meanwhile, the place where the examples
>> and apps initialize the 'split_hdr_size' field, and where the drivers
>> check if the 'split_hdr_size' value is 0 are also removed.
>>
>> User can still use `RTE_ETH_RX_OFFLOAD_BUFFER_SPLIT` for per-queue packet
>> split offload, which is configured by 'rte_eth_rxseg_split'.
>>
>> Signed-off-by: Xuan Ding <xuan.ding@intel.com>
>> ---
>> v2:
>> * fix CI build error
>> ---
>
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>
Rebased and applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-10-04 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 9:20 [PATCH] " xuan.ding
2022-08-12 3:13 ` [PATCH v2] " xuan.ding
2022-09-13 7:38 ` Andrew Rybchenko
2022-09-15 8:12 ` Ding, Xuan
2022-10-04 9:21 ` Andrew Rybchenko [this message]
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=b20ac171-2027-bede-92f8-06489b760768@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=aman.deep.singh@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chas3@att.com \
--cc=chenbo.xia@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=gakhil@marvell.com \
--cc=grive@u256.net \
--cc=humin29@huawei.com \
--cc=jasvinder.singh@intel.com \
--cc=jerinj@marvell.com \
--cc=jingjing.wu@intel.com \
--cc=junfeng.guo@intel.com \
--cc=kirankumark@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=lironh@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=mczekaj@marvell.com \
--cc=mdr@ashroe.eu \
--cc=ndabilpuram@marvell.com \
--cc=nicolas.chautru@intel.com \
--cc=orika@nvidia.com \
--cc=pbhagavatula@marvell.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=radu.nicolau@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
--cc=wenjun1.wu@intel.com \
--cc=xiao.w.wang@intel.com \
--cc=xuan.ding@intel.com \
--cc=yuying.zhang@intel.com \
--cc=zr@semihalf.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).