lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 25 Aug 2020 17:32:03 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Parav Pandit <parav@...lanox.com> Cc: davem@...emloft.net, netdev@...r.kernel.org, roid@...lanox.com, saeedm@...lanox.com, Jiri Pirko <jiri@...dia.com> Subject: Re: [PATCH net-next 2/3] devlink: Consider other controller while building phys_port_name On Tue, 25 Aug 2020 16:58:38 +0300 Parav Pandit wrote: > A devlink port may be for a controller consist of PCI device. > A devlink instance holds ports of two types 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 other system. > This is the case where a controller is located 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. > > When a devlink eswitch instance serves the devlink ports of both > controllers together, PCI PF/VF numbers may overlap. > Due to this a unique phys_port_name cannot be constructed. This description is clear as mud to me. Is it just me? Can someone understand this?
Powered by blists - more mailing lists