From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Jie Liu" <liujie5@linkdatatechnology.com>,
"Stephen Hemminger" <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: RE: sxe2 driver bug due to mempool layer violation
Date: Mon, 13 Jul 2026 16:07:29 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F6596B@smartserver.smartshare.dk> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F6596A@smartserver.smartshare.dk>
> From: Morten Brørup [mailto:mb@smartsharesystems.com]
> Sent: Monday, 13 July 2026 14.05
>
> Hi Jie Liu,
>
> Your sxe2 driver is accessing the flushthresh field in the mempool
> structure [1].
> This field is obsolete, as the mempool cache algorithm has been updated
> [2].
> If you need to bypass the mempool API and work directly with mempool
> internals, please keep your code up to date with the internals of the
> mempool library implementation.
>
> Please submit an updated version of your driver, or the patch to
> support AVX512 needs to be reverted. Jie Liu
As a temporary quick-fix, you can update the comparison on line 70 as:
- if (cache->len >= cache->flushthresh) {
+ if (cache->len > cache->size) {
>
> It looks like your driver introduced something similar to what the
> Intel common drivers were previously doing [3]; the Intel common
> drivers were updated accordingly [4].
>
> [1]: https://github.com/DPDK/dpdk/blob/v26.07-
> rc3/drivers/net/sxe2/sxe2_txrx_vec_avx512.c#L70
> [2]:
> https://github.com/DPDK/dpdk/commit/f5e1310f16e0909e7e7f71807123644c63b
> 23cba
> [3]:
> https://github.com/DPDK/dpdk/blob/v26.03/drivers/net/intel/common/tx.h#
> L315
> [4]:
> https://github.com/DPDK/dpdk/commit/062d6fe5d00d837ecb1a2b77b4a306e3619
> a7fde
>
prev parent reply other threads:[~2026-07-13 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 12:04 sxe2 driver bug due to mempool layer violation Morten Brørup
2026-07-13 14:07 ` Morten Brørup [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=98CBD80474FA8B44BF855DF32C47DC35F6596B@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=liujie5@linkdatatechnology.com \
--cc=stephen@networkplumber.org \
/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