From: Jiawei Wang <jiaweiw@nvidia.com>
To: <viacheslavo@nvidia.com>, <orika@nvidia.com>, <thomas@monjalon.net>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [PATCH v2 0/2] add new PHY affinity in the flow item and Tx queue API
Date: Mon, 30 Jan 2023 19:00:38 +0200 [thread overview]
Message-ID: <20230130170041.1360-1-jiaweiw@nvidia.com> (raw)
In-Reply-To: <http://patches.dpdk.org/project/dpdk/cover/20221221102934.13822-1-jiaweiw@nvidia.com/>
For the multiple hardware ports connect to a single DPDK port (mhpsdp),
currently, there is no information to indicate the packet belongs to
which hardware port.
This patch introduces a new phy affinity item in rte flow API, and
the phy affinity value reflects the physical phy affinity of the
received packets.
This patch adds the tx_phy_affinity setting in Tx queue API, the affinity value
reflects packets be sent to which hardware port.
While uses the phy affinity as a matching item in the flow, and sets the
same affinity on the tx queue, then the packet can be sent from the same
hardware port with received.
RFC: http://patches.dpdk.org/project/dpdk/cover/20221221102934.13822-1-jiaweiw@nvidia.com/
The PMD patch will be sent soon.
Jiawei Wang (2):
ethdev: add PHY affinity match item
ethdev: introduce the PHY affinity field in Tx queue API
app/test-pmd/cmdline.c | 84 +++++++++++++++++++++
app/test-pmd/cmdline_flow.c | 29 +++++++
devtools/libabigail.abignore | 5 ++
doc/guides/prog_guide/rte_flow.rst | 8 ++
doc/guides/rel_notes/release_23_03.rst | 5 ++
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 17 +++++
lib/ethdev/rte_ethdev.h | 7 ++
lib/ethdev/rte_flow.c | 1 +
lib/ethdev/rte_flow.h | 28 +++++++
9 files changed, 184 insertions(+)
--
2.18.1
next parent reply other threads:[~2023-01-30 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <http://patches.dpdk.org/project/dpdk/cover/20221221102934.13822-1-jiaweiw@nvidia.com/>
2023-01-30 17:00 ` Jiawei Wang [this message]
2023-01-30 17:00 ` [PATCH v2 1/2] ethdev: add PHY affinity match item Jiawei Wang
2023-01-31 14:36 ` Ori Kam
2023-02-01 8:50 ` Andrew Rybchenko
2023-02-01 14:59 ` Jiawei(Jonny) Wang
2023-01-30 17:00 ` [PATCH v2 2/2] ethdev: introduce the PHY affinity field in Tx queue API Jiawei Wang
2023-01-31 17:26 ` Thomas Monjalon
2023-02-01 9:45 ` Jiawei(Jonny) Wang
2023-02-01 9:05 ` Andrew Rybchenko
2023-02-01 15:50 ` Jiawei(Jonny) Wang
2023-02-02 9:28 ` Andrew Rybchenko
2023-02-02 14:43 ` Thomas Monjalon
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=20230130170041.1360-1-jiaweiw@nvidia.com \
--to=jiaweiw@nvidia.com \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@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).