From: Jakub Kicinski <k...@kernel.org> Date: Wed, 9 Sep 2020 08:34:42 -0700
> On Wed, 9 Sep 2020 07:50:32 +0300 Parav Pandit wrote: >> From: Parav Pandit <pa...@nvidia.com> >> >> Hi Jakub, Dave, >> >> Currently a devlink instance that supports an eswitch handles eswitch >> ports of two type of controllers. >> (1) controller discovered on same system where eswitch resides. >> This is the case where PCI PF/VF of a controller and devlink eswitch >> instance both are located on a single system. >> (2) controller located on external system. >> This is the case where a controller is plugged in one system and its >> devlink eswitch ports are located in a different system. In this case >> devlink instance of the eswitch only have access to ports of the >> controller. >> However, there is no way to describe that a eswitch devlink port >> belongs to which controller (mainly which external host controller). >> This problem is more prevalent when port attribute such as PF and VF >> numbers are overlapping between multiple controllers of same eswitch. >> Due to this, for a specific switch_id, unique phys_port_name cannot >> be constructed for such devlink ports. > > Acked-by: Jakub Kicinski <k...@kernel.org> Series applied, thanks everyone.
