diff options
author | Amit Cohen <amcohen@nvidia.com> | 2023-10-03 13:25:29 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2023-10-06 11:08:07 +0100 |
commit | 900f4285bbc2661e330036ee0fae046c7b79036b (patch) | |
tree | d865d765b22ab81136c9c3860d5154ddeced29b2 /tools | |
parent | 545535fd30dc8eaac96c09d774e8ba57bb247267 (diff) | |
download | linux-stable-900f4285bbc2661e330036ee0fae046c7b79036b.tar.gz linux-stable-900f4285bbc2661e330036ee0fae046c7b79036b.tar.bz2 linux-stable-900f4285bbc2661e330036ee0fae046c7b79036b.zip |
mlxsw: core_acl_flex_keys: Save chosen elements in all blocks per search
Currently, mlxsw_afk_picker() chooses which blocks will be used for a
given list of elements, and fills the blocks during the searching - when a
key block is found with most hits, it adds it and removes the elements from
the count of hits. This should be changed as we want to be able to choose
which blocks will be placed in blocks 0 to 5.
To separate between choosing blocks and filling blocks, several pre-changes
are required. Currently, the indication of whether all elements were
found in the chosen blocks is by the structure 'key_info->elusage'. This
structure is updated when block is filled as part of
mlxsw_afk_picker_key_info_add(). A following patch will call this
function only after choosing all the blocks. Add a bitmap called
'elusage_chosen' to store which elements were chosen in the chosen blocks.
Change the condition in the loop to check elements that were chosen, not
elements that were already filled in the blocks.
Signed-off-by: Amit Cohen <amcohen@nvidia.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
Signed-off-by: Petr Machata <petrm@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions