lkml.org 
[lkml]   [2021]   [Apr]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 4.14 36/68] net/mlx5: Fix placement of log_max_flow_counter
    Date
    From: Raed Salem <raeds@nvidia.com>

    [ Upstream commit a14587dfc5ad2312dabdd42a610d80ecd0dc8bea ]

    The cited commit wrongly placed log_max_flow_counter field of
    mlx5_ifc_flow_table_prop_layout_bits, align it to the HW spec intended
    placement.

    Fixes: 16f1c5bb3ed7 ("net/mlx5: Check device capability for maximum flow counters")
    Signed-off-by: Raed Salem <raeds@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>
    ---
    include/linux/mlx5/mlx5_ifc.h | 6 +++---
    1 file changed, 3 insertions(+), 3 deletions(-)

    diff --git a/include/linux/mlx5/mlx5_ifc.h b/include/linux/mlx5/mlx5_ifc.h
    index 6ffa181598e6..c4b8602ea6f5 100644
    --- a/include/linux/mlx5/mlx5_ifc.h
    +++ b/include/linux/mlx5/mlx5_ifc.h
    @@ -324,11 +324,11 @@ struct mlx5_ifc_flow_table_prop_layout_bits {
    u8 reserved_at_60[0x18];
    u8 log_max_ft_num[0x8];

    - u8 reserved_at_80[0x18];
    + u8 reserved_at_80[0x10];
    + u8 log_max_flow_counter[0x8];
    u8 log_max_destination[0x8];

    - u8 log_max_flow_counter[0x8];
    - u8 reserved_at_a8[0x10];
    + u8 reserved_at_a0[0x18];
    u8 log_max_flow[0x8];

    u8 reserved_at_c0[0x40];
    --
    2.30.2


    \
     
     \ /
      Last update: 2021-04-15 17:07    [W:3.323 / U:1.196 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site