From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by smtp.lore.kernel.org (Postfix) with ESMTP id EEF6EC43458 for ; Mon, 13 Jul 2026 12:04:42 +0000 (UTC) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BE43940276; Mon, 13 Jul 2026 14:04:41 +0200 (CEST) Received: from dkmailrelay1.smartsharesystems.com (smartserver.smartsharesystems.com [77.243.40.215]) by mails.dpdk.org (Postfix) with ESMTP id B9D3A40041 for ; Mon, 13 Jul 2026 14:04:38 +0200 (CEST) Received: from smartserver.smartsharesystems.com (smartserver.smartsharesys.local [192.168.4.10]) by dkmailrelay1.smartsharesystems.com (Postfix) with ESMTP id E46342033E; Mon, 13 Jul 2026 14:04:36 +0200 (CEST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: sxe2 driver bug due to mempool layer violation Date: Mon, 13 Jul 2026 14:04:35 +0200 Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F6596A@smartserver.smartshare.dk> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: sxe2 driver bug due to mempool layer violation Thread-Index: Ad0Sv8V+9EqmdmljRiqV2lDLvHpGjA== X-MimeOLE: Produced By Microsoft Exchange V6.5 From: =?iso-8859-1?Q?Morten_Br=F8rup?= To: "Jie Liu" , "Stephen Hemminger" Cc: X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 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. 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_v= ec_avx512.c#L70 [2]: = https://github.com/DPDK/dpdk/commit/f5e1310f16e0909e7e7f71807123644c63b23= cba [3]: = https://github.com/DPDK/dpdk/blob/v26.03/drivers/net/intel/common/tx.h#L3= 15 [4]: = https://github.com/DPDK/dpdk/commit/062d6fe5d00d837ecb1a2b77b4a306e3619a7= fde Venlig hilsen / Kind regards, -Morten Br=F8rup