All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Subject: [PATCH v2 0/2] I40E refactors
Date: Fri, 21 Aug 2026 10:15:29 +0100	[thread overview]
Message-ID: <cover.1787303683.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <cover.1787149329.git.anatoly.burakov@intel.com>

A small amount of refactor in hash engine to prepare for future
code. Specifically, disentangling the mutable filter list metadata
from immutable RSS configuration supplied from rte_flow API, and
getting rid of embedded rte_flow RSS conf struct and replacing it
with direct values embedded in config struct.

v1 -> v2:
- Fix patch 1 returning non-NULL pointers to queue/key when lengths
  of either are 0

Anatoly Burakov (2):
  net/i40e: do not use flow RSS conf struct
  net/i40e: move mutable fields out of RSS config

 drivers/net/intel/i40e/i40e_ethdev.h |  18 +++-
 drivers/net/intel/i40e/i40e_flow.c   |  13 ++-
 drivers/net/intel/i40e/i40e_hash.c   | 125 +++++++++++++--------------
 drivers/net/intel/i40e/i40e_hash.h   |   1 -
 4 files changed, 83 insertions(+), 74 deletions(-)

-- 
2.52.0


  parent reply	other threads:[~2026-08-21  9:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19 14:23 [PATCH v1 0/2] I40E refactors Anatoly Burakov
2026-08-19 14:23 ` [PATCH v1 1/2] net/i40e: do not use flow RSS conf struct Anatoly Burakov
2026-08-19 14:23 ` [PATCH v1 2/2] net/i40e: move mutable fields out of RSS config Anatoly Burakov
2026-08-21  9:15 ` Anatoly Burakov [this message]
2026-08-21  9:15   ` [PATCH v2 1/2] net/i40e: do not use flow RSS conf struct Anatoly Burakov
2026-08-21  9:15   ` [PATCH v2 2/2] net/i40e: move mutable fields out of RSS config Anatoly Burakov

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=cover.1787303683.git.anatoly.burakov@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.