From: Raslan Darawsheh <rasland@nvidia.com>
To: "Sean Zhang (Networking SW)" <xiazhang@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [v4] net/mlx5: support matching flow on port representor ID
Date: Tue, 25 Oct 2022 13:52:39 +0000 [thread overview]
Message-ID: <BYAPR12MB307881070BE563811867618BCF319@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20221025063037.266580-1-xiazhang@nvidia.com>
Hi,
> -----Original Message-----
> From: Sean Zhang <xiazhang@nvidia.com>
> Sent: Tuesday, October 25, 2022 9:31 AM
> To: NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>;
> Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>
> Cc: dev@dpdk.org
> Subject: [v4] net/mlx5: support matching flow on port representor ID
>
> Add support for port_representor item, it will match on traffic originated
> from representor port specified in the pattern. This item is supported in FDB
> steering domain only (in the flow with transfer attribute).
>
> For example, below flow will redirect the destination of traffic from ethdev 1
> to ethdev 2.
>
> testpmd> ... pattern eth / port_representor port_id is 1 / end actions
> represented_port ethdev_port_id 2 / ...
>
> To handle abovementioned item, Tx queue matching is added in the driver,
> and the flow will be expanded to number of the Tx queues. If the spec of
> port_representor is NULL, the flow will not be expanded and match on traffic
> from any representor port.
>
> Signed-off-by: Sean Zhang <xiazhang@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
> The depending patches as below:
>
> [1] http://patches.dpdk.org/project/dpdk/cover/20220930125315.5079-1-
> suanmingm@nvidia.com
> ---
> v4 - update the commit title
> v3 - rebase to the latest version
> v2 - commit message updated and add missing feature in doc
> ---
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2022-10-25 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 14:57 [PATCH] net/mlx5: add port representor support Sean Zhang
2022-10-19 15:43 ` Ivan Malov
2022-10-20 1:24 ` Sean Zhang (Networking SW)
2022-10-20 1:20 ` [v2] net/mlx5: add port representor item support Sean Zhang
2022-10-20 8:20 ` Slava Ovsiienko
2022-10-24 1:48 ` [v3] " Sean Zhang
2022-10-24 15:27 ` Thomas Monjalon
2022-10-25 6:30 ` [v4] net/mlx5: support matching flow on port representor ID Sean Zhang
2022-10-25 13:52 ` Raslan Darawsheh [this message]
2022-10-24 15:26 ` [PATCH] net/mlx5: add port representor support 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=BYAPR12MB307881070BE563811867618BCF319@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
--cc=xiazhang@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).