netdev - Re: [net-next PATCH 1/5] octeontx2-af: add support for custom KPU entries

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20210526170630.1732c4b6@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Wed, 26 May 2021 17:06:30 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     George Cherian <george.cherian@...vell.com>
Cc:     <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <davem@...emloft.net>, <gcherian@...vell.com>,
        <sgoutham@...vell.com>
Subject: Re: [net-next PATCH 1/5] octeontx2-af: add support for custom KPU
 entries

On Wed, 26 May 2021 21:26:52 +0530 George Cherian wrote:
> From: Stanislaw Kardach <skardach@...vell.com>
> 
> Add ability to load a set of custom KPU entries. This
> allows for flexible support for custom protocol parsing.
> 
> AF driver will attempt to load the profile and verify if it can fit
> hardware capabilities. If not, it will revert to the built-in profile.
> 
> Next it will replace the first KPU_MAX_CST_LT (2) entries in each KPU
> in default profile with entries read from the profile image.
> The built-in profile should always contain KPU_MAX_CSR_LT first no-match
> entries and AF driver will disable those in the KPU unless custom
> profile is loaded.
> 
> Profile file contains also a list of default protocol overrides to
> allow for custom protocols to be used there.
> 
> Signed-off-by: Stanislaw Kardach <skardach@...vell.com>
> Signed-off-by: George Cherian <george.cherian@...vell.com>

This one does not build.