From: Thomas Monjalon <thomas@monjalon.net>
To: Sean Zhang <xiazhang@nvidia.com>
Cc: Matan Azrad <matan@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
dev@dpdk.org
Subject: Re: [v3] net/mlx5: add port representor item support
Date: Mon, 24 Oct 2022 17:27:58 +0200 [thread overview]
Message-ID: <4776853.31r3eYUQgx@thomas> (raw)
In-Reply-To: <20221024014815.10598-1-xiazhang@nvidia.com>
As title, I suggest:
net/mlx5: support matching flow on port representor ID
24/10/2022 03:48, Sean Zhang:
> 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>
next prev parent reply other threads:[~2022-10-24 15:28 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 [this message]
2022-10-25 6:30 ` [v4] net/mlx5: support matching flow on port representor ID Sean Zhang
2022-10-25 13:52 ` Raslan Darawsheh
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=4776853.31r3eYUQgx@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.