From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Subject: [PATCH v1 0/6] Centralize flow memory management in ICE
Date: Tue, 20 Oct 2026 13:11:03 +0100 [thread overview]
Message-ID: <cover.1792498154.git.anatoly.burakov@intel.com> (raw)
This patchset rolls in a few fixes for flow engines, but the
main point is to rework the flow engines to have more defined
memory management.
Anatoly Burakov (6):
net/ice: release ACL slot on entry creation failure
net/ice: fix inconsistent state on FDIR failure
net/ice: standardize VOID handling in flow parsers
net/ice: remove temporary flow pattern buffer
net/ice: use caller-owned pattern match storage
net/ice: centralize flow rule memory management
drivers/net/intel/ice/ice_acl_filter.c | 91 +++++---------
drivers/net/intel/ice/ice_ethdev.h | 2 -
drivers/net/intel/ice/ice_fdir_filter.c | 124 ++++++++-----------
drivers/net/intel/ice/ice_generic_flow.c | 141 ++++++----------------
drivers/net/intel/ice/ice_generic_flow.h | 25 +++-
drivers/net/intel/ice/ice_hash.c | 87 ++++---------
drivers/net/intel/ice/ice_switch_filter.c | 97 ++++-----------
7 files changed, 185 insertions(+), 382 deletions(-)
--
2.52.0
next reply other threads:[~2026-10-20 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 12:11 Anatoly Burakov [this message]
2026-10-20 12:11 ` [PATCH v1 1/6] net/ice: release ACL slot on entry creation failure Anatoly Burakov
2026-10-20 12:11 ` [PATCH v1 2/6] net/ice: fix inconsistent state on FDIR failure Anatoly Burakov
2026-10-20 12:11 ` [PATCH v1 3/6] net/ice: standardize VOID handling in flow parsers Anatoly Burakov
2026-10-20 12:11 ` [PATCH v1 4/6] net/ice: remove temporary flow pattern buffer Anatoly Burakov
2026-10-20 12:11 ` [PATCH v1 5/6] net/ice: use caller-owned pattern match storage Anatoly Burakov
2026-10-20 12:11 ` [PATCH v1 6/6] net/ice: centralize flow rule memory management 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.1792498154.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox