From: Jiawei Wang <jiaweiw@nvidia.com>
To: <viacheslavo@nvidia.com>, <orika@nvidia.com>, <thomas@monjalon.net>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [RFC 0/5] add new port affinity item and affinity in Tx queue API
Date: Wed, 21 Dec 2022 12:29:29 +0200 [thread overview]
Message-ID: <20221221102934.13822-1-jiaweiw@nvidia.com> (raw)
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 port affinity item in rte flow API, and
the port affinity value reflects the physical port affinity of the
received packets.
The example of match the affinity item:
testpmd> flow create 0 ingress group 0 pattern port_affinity affinity is 1 /
end actions queue index 0 / end
This patch adds the tx_affinity setting in Tx queue API, the affinity value
reflects packets be sent to which hardware port.
The testpmd command format as below:
testpmd> port config (port_id) txq (queue_id) affinity (value)
While uses the port 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.
Jiawei Wang (5):
ethdev: add port affinity match item
ethdev: introduce the affinity field in Tx queue API
drivers: add lag Rx port affinity in PRM
net/mlx5: add port affinity item support
drivers: enhance the Tx queue affinity
app/test-pmd/cmdline.c | 84 ++++++++++++++++++
app/test-pmd/cmdline_flow.c | 29 +++++++
devtools/libabigail.abignore | 5 ++
doc/guides/nics/features/mlx5.ini | 1 +
doc/guides/nics/mlx5.rst | 4 +-
doc/guides/prog_guide/rte_flow.rst | 7 ++
doc/guides/rel_notes/release_22_03.rst | 9 ++
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 17 ++++
drivers/common/mlx5/mlx5_devx_cmds.c | 3 +
drivers/common/mlx5/mlx5_devx_cmds.h | 1 +
drivers/common/mlx5/mlx5_prm.h | 15 ++--
drivers/net/mlx5/linux/mlx5_os.c | 6 ++
drivers/net/mlx5/mlx5.c | 43 +++++-----
drivers/net/mlx5/mlx5.h | 3 +
drivers/net/mlx5/mlx5_devx.c | 21 +++--
drivers/net/mlx5/mlx5_flow.h | 3 +
drivers/net/mlx5/mlx5_flow_dv.c | 95 +++++++++++++++++++++
drivers/net/mlx5/mlx5_flow_hw.c | 14 +++
drivers/net/mlx5/mlx5_tx.h | 1 +
drivers/net/mlx5/mlx5_txq.c | 9 ++
lib/ethdev/rte_ethdev.h | 1 +
lib/ethdev/rte_flow.c | 1 +
lib/ethdev/rte_flow.h | 28 ++++++
23 files changed, 357 insertions(+), 43 deletions(-)
--
2.18.1
next reply other threads:[~2022-12-21 10:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 10:29 Jiawei Wang [this message]
2022-12-21 10:29 ` [RFC 1/5] ethdev: add port affinity match item Jiawei Wang
2023-01-11 16:41 ` Ori Kam
2023-01-18 11:07 ` Thomas Monjalon
2023-01-18 14:41 ` Jiawei(Jonny) Wang
2023-01-18 16:26 ` Thomas Monjalon
2023-01-24 14:00 ` Jiawei(Jonny) Wang
2022-12-21 10:29 ` [RFC 2/5] ethdev: introduce the affinity field in Tx queue API Jiawei Wang
2023-01-11 16:47 ` Ori Kam
2023-01-18 11:37 ` Thomas Monjalon
2023-01-18 14:44 ` Jiawei(Jonny) Wang
2023-01-18 16:31 ` Thomas Monjalon
2023-01-24 13:32 ` Jiawei(Jonny) Wang
2022-12-21 10:29 ` [RFC 3/5] drivers: add lag Rx port affinity in PRM Jiawei Wang
2022-12-21 10:29 ` [RFC 4/5] net/mlx5: add port affinity item support Jiawei Wang
2022-12-21 10:29 ` [RFC 5/5] drivers: enhance the Tx queue affinity Jiawei Wang
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=20221221102934.13822-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).