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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190228133209.GA2462@nanopsycho>
Date:   Thu, 28 Feb 2019 14:32:09 +0100
From:   Jiri Pirko <jiri@...nulli.us>
To:     Jakub Kicinski <jakub.kicinski@...ronome.com>
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

Thu, Feb 28, 2019 at 09:56:24AM CET, jiri@...nulli.us wrote:

[...]


>>devlink instance).  Those less pipelined NICs can forward between
>>ports, but still want a function per port (otherwise user space
>>sometimes gets confused).  If we have multiple functions which are on
>>the same "switchid" they should have a single devlink instance if you
>>ask me.  That instance will have all the ports of the device.
>
>Okay, that makes sense. But the question it, can the same devlink
>instance contain ports that does not have "Switchid"?
>
>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.

Working on this. Will sent patchset later today/tmrw.

[...]

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ