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
| ||
|
Message-ID: <20190301080401.1b860467@cakuba.netronome.com> Date: Fri, 1 Mar 2019 08:04:01 -0800 From: Jakub Kicinski <jakub.kicinski@...ronome.com> To: Jiri Pirko <jiri@...nulli.us> Cc: davem@...emloft.net, oss-drivers@...ronome.com, netdev@...r.kernel.org, parav@...lanox.com, jgg@...lanox.com Subject: Re: [PATCH net-next 4/8] devlink: allow subports on devlink PCI ports On Fri, 1 Mar 2019 08:25:57 +0100, Jiri Pirko wrote: > >> I think it would be beneficial to have the switchid shown for devlink > >> ports too. Then it is clean that the devlink ports with the same > >> switchid belong to the same switch, and other ports under the same > >> devlink instance (like PF itself) is separate, but still under the same > >> ASIC. > > > >Sure, you mean in terms of UI - user space can do a link dump or get > >that from sysfs, right? > > I thinking about moving it to devlink. I'll work on it more today. At the kernel level? Are we sure this is appropriate? I'd think switchid is in essence a forwarding attribute, so it belongs with netdevs, no?
Powered by blists - more mailing lists