DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: add wire vport hint
Date: Tue, 17 Nov 2020 16:18:19 +0000	[thread overview]
Message-ID: <DM6PR12MB27488D838FEDA2D22F1E6E2BCFE20@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1605281572-31195-1-git-send-email-viacheslavo@nvidia.com>


> -----Original Message-----
> From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> Sent: Friday, November 13, 2020 5:33 PM
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@nvidia.com>; Matan Azrad
> <matan@nvidia.com>
> Subject: [PATCH] net/mlx5: add wire vport hint
> The kernel can use two approaches to distinguish the E-Switch
> source vport in the packet metadata - either with dedicated
> source_port field or register C0. To eliminate the extra source
> vport matching in the hardware the source_port field can be
> set to specific values (0xFFFF) for the wire source port.
> This match can be applied to recognize wire port only in FDB
> domain. Missing the register C0 match in the NIC Rx domain causes
> incorrect representor steering within shared IB device ports
> and must be always specified (if kernel uses this approach).
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
>  drivers/net/mlx5/mlx5_flow_dv.c | 39
> +++++++++++++++++++++++++++++----------
>  1 file changed, 29 insertions(+), 10 deletions(-)

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2020-11-17 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 15:32 Viacheslav Ovsiienko
2020-11-17 16:18 ` Raslan Darawsheh [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR12MB27488D838FEDA2D22F1E6E2BCFE20@DM6PR12MB2748.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=viacheslavo@nvidia.com \


* 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).