DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: luca.boccassi@gmail.com, stable@dpdk.org, dsosnowski@nvidia.com,
	maxime.peim@gmail.com
Cc: dev@dpdk.org, Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
	David Christensen <drc@linux.vnet.ibm.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Ian Stokes <ian.stokes@intel.com>,
	Jerin Jacob <jerinj@marvell.com>,
	John McNamara <john.mcnamara@intel.com>,
	Ju-Hyoung Lee <juhlee@microsoft.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Yanghang Liu <yanghliu@redhat.com>,
	sbadawi@nvidia.com, waela@nvidia.com
Subject: Re: 24.11.7 patches review and test
Date: Tue, 4 Aug 2026 16:46:14 +0300	[thread overview]
Message-ID: <c49e8480-5d4d-459d-bf8d-c73321c42abb@nvidia.com> (raw)
In-Reply-To: <20260727094306.41797-1-luca.boccassi@gmail.com>

On 7/27/26 12:43 PM, luca.boccassi@gmail.com wrote:

> Hi all,
>
> Here is a list of patches targeted for stable release 24.11.7.The planned date for the final release is 2026/08/10.
>
> Please help with testing and validation of your use cases and report
> any issues/results with reply-all to this mail. For the final release
> the fixes and reported validations will be added to the release notes.
>
> A release candidate tarball can be found at:
>
>      https://dpdk.org/browse/dpdk-stable/tag/?id=v24.11.7-rc1
>
> These patches are located at branch 24.11 of dpdk-stable repo:
>      https://dpdk.org/browse/dpdk-stable/
>
> Thanks.
>
> Luca Boccassi
>
> ---
[..]
> Maxime Peim (1):
>        net/mlx5: prepend implicit items in sync flow creation
[..]

Hello Maxime, Luca,

Commit 471350f6cd ("net/mlx5: prepend implicit items in sync flow 
creation") on 24.11 regresses eSwitch HWS when representor matching is 
disabled (repr_matching_en=0): traffic that should hit PF NIC Rx rules 
after FDB transfer is no longer received.

The backport dropped the priv->sh->config.repr_matching checks that 
previously gated implicit REPRESENTED_PORT / REG_C_0 prepending. That is 
correct on upstream main after repr_matching_en was removed 
(c41f621786), but on 24.11 the option still exists and, when off, TX 
representor tagging is not set up. Unconditionally prepending those 
matches then scopes NIC rules incorrectly.

Dariusz volunteered to send a fix.

We will send our full report soon.

Regards,
Ali


  reply	other threads:[~2026-08-04 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27  9:43 24.11.7 patches review and test luca.boccassi
2026-08-04 13:46 ` Ali Alnubani [this message]
2026-08-05 10:35   ` Dariusz Sosnowski
2026-08-05 11:07   ` Kevin Traynor

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=c49e8480-5d4d-459d-bf8d-c73321c42abb@nvidia.com \
    --to=alialnu@nvidia.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=dsosnowski@nvidia.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=ian.stokes@intel.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=juhlee@microsoft.com \
    --cc=ktraynor@redhat.com \
    --cc=luca.boccassi@gmail.com \
    --cc=maxime.peim@gmail.com \
    --cc=pezhang@redhat.com \
    --cc=rasland@nvidia.com \
    --cc=sbadawi@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=waela@nvidia.com \
    --cc=yanghliu@redhat.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