From: Stephen Hemminger <stephen@networkplumber.org>
To: Maxime Leroy <maxime@leroys.fr>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/6] net/dpaa2: RSS fixes and improvements
Date: Tue, 16 Jun 2026 15:07:35 -0700 [thread overview]
Message-ID: <20260616150735.48bdef03@phoenix.local> (raw)
In-Reply-To: <20260616104717.723087-1-maxime@leroys.fr>
On Tue, 16 Jun 2026 12:47:09 +0200
Maxime Leroy <maxime@leroys.fr> wrote:
> A set of RSS fixes and improvements for the dpaa2 PMD.
>
> Patches 1 and 2 fix the RSS hash key: the L4 destination port was never
> added (both extracts used the source port), and SCTP now uses the same L4
> port extraction as TCP/UDP. Both are tagged for stable.
>
> Patches 3 and 4 are small cleanups in the key builder (a dead num_extracts
> increment, and the unset PPPoE guard flag).
>
> Patch 5 honours RTE_ETH_RSS_LEVEL_INNERMOST so tunnelled traffic hashes on
> the inner IP header. Patch 6 implements reta_query / reta_update as an
> emulation over the HW distribution-size mechanism, since dpaa2 has no
> software-visible indirection table.
>
> Tested on LX2160A (lx2160acex7).
Applied to next-net
prev parent reply other threads:[~2026-06-16 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 10:47 [PATCH 0/6] net/dpaa2: RSS fixes and improvements Maxime Leroy
2026-06-16 10:47 ` [PATCH 1/6] net/dpaa2: add L4 destination port to the RSS hash key Maxime Leroy
2026-06-16 10:47 ` [PATCH 2/6] net/dpaa2: use L4 port extraction for SCTP RSS Maxime Leroy
2026-06-16 10:47 ` [PATCH 3/6] net/dpaa2: drop stray extract count bump in RSS key build Maxime Leroy
2026-06-16 10:47 ` [PATCH 4/6] net/dpaa2: set PPPoE configured flag " Maxime Leroy
2026-06-16 10:47 ` [PATCH 5/6] net/dpaa2: support inner RSS level for tunnelled traffic Maxime Leroy
2026-06-16 10:47 ` [PATCH 6/6] net/dpaa2: implement RSS RETA query and update Maxime Leroy
2026-06-16 22:07 ` Stephen Hemminger [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=20260616150735.48bdef03@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=maxime@leroys.fr \
/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