From: "Xu, HailinX" <hailinx.xu@intel.com>
To: "Zeng, ZhichaoX" <zhichaox.zeng@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Zeng, ZhichaoX" <zhichaox.zeng@intel.com>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
"Shahaf Shuler" <shahafs@nvidia.com>
Subject: RE: [PATCH] examples/ip_reassembly: remove conflicting Tx offload
Date: Sun, 28 Sep 2025 09:04:10 +0000 [thread overview]
Message-ID: <DS4PPF653E4B5319321D7269925038504289F18A@DS4PPF653E4B531.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20250919071213.818567-1-zhichaox.zeng@intel.com>
> -----Original Message-----
> From: Zhichao Zeng <zhichaox.zeng@intel.com>
> Sent: Friday, September 19, 2025 3:12 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Zeng, ZhichaoX <zhichaox.zeng@intel.com>; Konstantin
> Ananyev <konstantin.ananyev@huawei.com>; Ferruh Yigit
> <ferruh.yigit@amd.com>; Shahaf Shuler <shahafs@nvidia.com>
> Subject: [PATCH] examples/ip_reassembly: remove conflicting Tx offload
>
> IP packet reassembly requires the MULTI_SEGS offload to be enabled in order
> to handle fragmented packets across multiple memory segments. However,
> the MBUF_FAST_FREE offload conflicts with MULTI_SEGS and cannot be
> enabled simultaneously.
>
> Remove the MBUF_FAST_FREE offload to avoid conflicts with MULTI_SEGS.
>
> Fixes: 9df56e69ee3f ("examples/ip_reassembly: convert to new ethdev
> offloads API")
> Cc: stable@dpdk.org
>
> Signed-off-by: Zhichao Zeng <zhichaox.zeng@intel.com>
> ---
Tested-by: Xu, HailinX <hailinx.xu@intel.com>
prev parent reply other threads:[~2025-09-28 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 7:12 Zhichao Zeng
2025-09-19 7:13 ` Konstantin Ananyev
2025-09-28 9:04 ` Xu, HailinX [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=DS4PPF653E4B5319321D7269925038504289F18A@DS4PPF653E4B531.namprd11.prod.outlook.com \
--to=hailinx.xu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=konstantin.ananyev@huawei.com \
--cc=shahafs@nvidia.com \
--cc=stable@dpdk.org \
--cc=zhichaox.zeng@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).