From: Thomas Monjalon <thomas@monjalon.net>
To: Shani Peretz <shperetz@nvidia.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3 0/2] Add jump flow support and queue menegment with new snippets
Date: Wed, 17 Sep 2025 10:45:51 +0200 [thread overview]
Message-ID: <3252380.ElGaqSPkdT@thomas> (raw)
In-Reply-To: <20250825072346.25548-1-shperetz@nvidia.com>
25/08/2025 09:23, Shani Peretz:
> v3:
> add comma in the meson.build file to fix build error
>
> v2:
> sent mistakely as RFC - remove RFC tag, no functional changes
>
> v1:
> This patch series adds port affinity matching for bonded ports and
> refactors queue management to support the new port affinity snippets.
> This refactoring also enables other snippets that require access to
> the queue number to utilize it more easily.
>
> It also introduces support for jumping to specific flow groups,
> with three new snippets demonstrating this feature.
>
> Shani Peretz (2):
> examples/flow_filtering: add match port affinity snippet
> examples/flow_filtering: add jump flow
Removed few doubled blanked lines,
and reworded title like this:
examples/flow_filtering: add snippets using jump
examples/flow_filtering: add port affinity snippet
Applied, thanks.
next prev parent reply other threads:[~2025-09-17 8:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 7:15 [RFC PATCH " Shani Peretz
2025-06-24 7:15 ` [RFC PATCH 1/2] examples/flow_filtering: add match port affinity snippet Shani Peretz
2025-08-11 14:37 ` [PATCH v2 0/2] Add jump flow support and queue menegment with new snippets Shani Peretz
2025-08-11 14:37 ` [PATCH v2 1/2] examples/flow_filtering: add match port affinity snippet Shani Peretz
2025-08-25 7:23 ` [PATCH v3 0/2] Add jump flow support and queue menegment with new snippets Shani Peretz
2025-08-25 7:23 ` [PATCH v3 1/2] examples/flow_filtering: add match port affinity snippet Shani Peretz
2025-08-25 7:23 ` [PATCH v3 2/2] examples/flow_filtering: add jump flow Shani Peretz
2025-09-17 8:45 ` Thomas Monjalon [this message]
2025-08-11 14:37 ` [PATCH v2 " Shani Peretz
2025-06-24 7:15 ` [RFC PATCH " Shani Peretz
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=3252380.ElGaqSPkdT@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=shperetz@nvidia.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;
as well as URLs for NNTP newsgroup(s).