netdev - Re: [PATCH net-next 1/2] mlxsw: Register physical ports as a devlink resource

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]

Date:   Tue, 12 Jan 2021 20:21:22 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Ido Schimmel <idosch@...sch.org>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, jiri@...dia.com,
        danieller@...dia.com, mlxsw@...dia.com,
        Ido Schimmel <idosch@...dia.com>
Subject: Re: [PATCH net-next 1/2] mlxsw: Register physical ports as a
 devlink resource

On Tue, 12 Jan 2021 10:39:30 +0200 Ido Schimmel wrote:
> From: Danielle Ratson <danieller@...dia.com>
> 
> The switch ASIC has a limited capacity of physical ('flavour physical'
> in devlink terminology) ports that it can support. While each system is
> brought up with a different number of ports, this number can be
> increased via splitting up to the ASIC's limit.
> 
> Expose physical ports as a devlink resource so that user space will have
> visibility to the maximum number of ports that can be supported and the
> current occupancy.

Any thoughts on making this a "generic" resource?

The limitation on number of logical ports is pretty common for switches.