netdev - Re: [PATCH net-next 00/15] mlxsw: spectrum: Prepare for XM implementation

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] [day] [month] [year] [list]

Date:   Thu, 12 Nov 2020 15:59:29 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Ido Schimmel <idosch@...sch.org>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, jiri@...dia.com,
        mlxsw@...dia.com, Ido Schimmel <idosch@...dia.com>
Subject: Re: [PATCH net-next 00/15] mlxsw: spectrum: Prepare for XM
 implementation - prefix insertion and removal

On Tue, 10 Nov 2020 11:48:45 +0200 Ido Schimmel wrote:
> Jiri says:
> 
> This is a preparation patchset for follow-up support of boards with
> extended mezzanine (XM), which is going to allow extended (scale-wise)
> router offload.
> 
> XM requires a separate PRM register named XMDR to be used instead of
> RALUE to insert/update/remove FIB entries. Therefore, this patchset
> extends the previously introduces low-level ops to be able to have
> XM-specific FIB entry config implementation.
> 
> Currently the existing original RALUE implementation is moved to "basic"
> low-level ops.
> 
> Unlike legacy router, insertion/update/removal of FIB entries into XM
> could be done in bulks up to 4 items in a single PRM register write.
> That is why this patchset implements "an op context", that allows the
> future XM ops implementation to squash multiple FIB events to single
> register write. For that, the way in which the FIB events are processed
> by the work queue has to be changed.
> 
> The conversion from 1:1 FIB event - work callback call to event queue is
> implemented in patch #3.
> 
> Patch #4 introduces "an op context" that will allow in future to squash
> multiple FIB events into one XMDR register write. Patch #12 converts it
> from stack to be allocated per instance.
> 
> Existing RALUE manipulations are pushed to ops in patch #10.
> 
> Patch #13 is introducing a possibility for low-level implementation to
> have per FIB entry private memory.
> 
> The rest of the patches are either cosmetics or smaller preparations.

Applied, thanks!