[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210413132142.0e2d1752@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Tue, 13 Apr 2021 13:21:42 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Saeed Mahameed <saeed@...nel.org>
Cc: "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Tariq Toukan <tariqt@...dia.com>,
Parav Pandit <parav@...dia.com>, Roi Dayan <roid@...dia.com>,
Vu Pham <vuhuong@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>
Subject: Re: [net-next 01/16] net/mlx5: E-Switch, let user to enable disable
metadata
On Tue, 13 Apr 2021 12:29:51 -0700 Saeed Mahameed wrote:
> Currently each packet inserted in eswitch is tagged with a internal
> metadata to indicate source vport. Metadata tagging is not always
> needed. Metadata insertion is needed for multi-port RoCE, failover
> between representors and stacked devices. In many other cases,
> metadata enablement is not needed.
>
> Metadata insertion slows down the packet processing rate.
Can you share example numbers?
> Hence, allow user to disable metadata using driver specific devlink
> parameter.
>
> Example to show and disable metadata before changing eswitch mode:
> $ devlink dev param show pci/0000:06:00.0 name esw_port_metadata
> pci/0000:06:00.0:
> name esw_port_metadata type driver-specific
> values:
> cmode runtime value true
>
> $ devlink dev param set pci/0000:06:00.0 \
> name esw_port_metadata value false cmode runtime
>
> $ devlink dev eswitch set pci/0000:06:00.0 mode switchdev
Is this something that only gets enabled when device is put into
switchdev mode? That needs to be clarified in the documentation IMO
to give peace of mind to all users who don't enable switchdev.
Powered by blists - more mailing lists