On Tue, 15 Dec 2020 01:03:52 -0800 Saeed Mahameed wrote: > From: Vu Pham <vuhu...@nvidia.com> > > Prepare eswitch to handle SF vport during > (a) querying eswitch functions > (b) egress ACL creation > (c) account for SF vports in total vports calculation > > Assign a dedicated placeholder for SFs vports and their representors. > They are placed after VFs vports and before ECPF vports as below: > [PF,VF0,...,VFn,SF0,...SFm,ECPF,UPLINK]. > > Change functions to map SF's vport numbers to indices when > accessing the vports or representors arrays, and vice versa. > > Signed-off-by: Vu Pham <vuhu...@nvidia.com> > Signed-off-by: Parav Pandit <pa...@nvidia.com> > Reviewed-by: Roi Dayan <r...@nvidia.com> > Signed-off-by: Saeed Mahameed <sae...@nvidia.com>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/Kconfig > b/drivers/net/ethernet/mellanox/mlx5/core/Kconfig > index d6c48582e7a8..ad45d20f9d44 100644 > --- a/drivers/net/ethernet/mellanox/mlx5/core/Kconfig > +++ b/drivers/net/ethernet/mellanox/mlx5/core/Kconfig > @@ -212,3 +212,13 @@ config MLX5_SF > Build support for subfuction device in the NIC. A Mellanox subfunction > device can support RDMA, netdevice and vdpa device. > It is similar to a SRIOV VF but it doesn't require SRIOV support. > + > +config MLX5_SF_MANAGER > + bool > + depends on MLX5_SF && MLX5_ESWITCH > + default y > + help > + Build support for subfuction port in the NIC. A Mellanox subfunction > + port is managed through devlink. A subfunction supports RDMA, netdevice > + and vdpa device. It is similar to a SRIOV VF but it doesn't require > + SRIOV support. Why is this a separate knob? And it's not used anywhere AFAICS.
