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  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:   Mon, 20 Jul 2020 11:04:42 +0000
From:   Xiaoliang Yang <>
To:     "Allan W. Nielsen" <>,
        Vladimir Oltean <>
CC:     Joergen Andreasen <>,
        Po Liu <>,
        Claudiu Manoil <>,
        Alexandru Marginean <>,
        Vladimir Oltean <>,
        Leo Li <>, Mingkai Hu <>,
        Andrew Lunn <>,
        Florian Fainelli <>,
        Vivien Didelot <>,
        "David S. Miller" <>,
        Jiri Pirko <>,
        Ido Schimmel <>,
        Jakub Kicinski <>,
        Vinicius Costa Gomes <>,
        Nikolay Aleksandrov <>,
        Roopa Prabhu <>,
        netdev <>,
        lkml <>,
        Horatiu Vultur <>,
        Alexandre Belloni <>,
        Microchip Linux Driver Support <>,
        "" <>
Subject: RE: [EXT] Re: [PATCH v2 net-next 03/10] net: mscc: ocelot: allocated
 rules to different hardware VCAP TCAMs by chain index

18.07.2020 3:10, Allan wrote:
> Okay - I will need to look deeper into to this to really understand the consequences of mixing different types of filters. As far as Joergens example goes, "matchall" is really the same as a flower without any matches.
> Long story short, to me the most important step here is that we come up with a design where we can expose the 3 lookups in IS1 as separate chains, and that we have something which behaves the same in HW and SW.
> Once we have that, we can add templates, shared blocks, shared actions etc. in the future.
> I know I have not been very active on this thread for the past couple of days, but I'm certainly interesting in continue working/reviewing this.
> I will be OOO for the next 3 weeks, with very limited options for reviewing/commenting on this, but after that I'm back again.

So chain template is used to configure key type on IS1, we can set one key type for each of the three lookups. In order to support all key types, we need to add half keys, full keys and quard keys support. If there is no template set, using a default "S1_7TUPLE" key type, which can cover most keys.

In general, using a default key type for each of the three lookups, and limited one action on one lookup chain, these can support three parallel lookup on IS1. Add PAG support as two lookups on IS2, then templates and shared blocks can be supported after that.


Powered by blists - more mailing lists