netdev - Re: [PATCH mlx5-next 4/4] net/mlx5: Move flow counters data structures from flow steering header

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

Message-ID: <CAM_iQpX4W4svScQC+49gbx84om4gRLa9L5oKP01-H23ZuQ-PNw@mail.gmail.com>
Date:   Tue, 4 Dec 2018 21:04:43 -0800
From:   Cong Wang <xiyou.wangcong@...il.com>
To:     Saeed Mahameed <saeedm@...lanox.com>
Cc:     leonro@...lanox.com,
        Linux Kernel Network Developers <netdev@...r.kernel.org>,
        linux-rdma@...r.kernel.org, Jason Gunthorpe <jgg@...lanox.com>
Subject: Re: [PATCH mlx5-next 4/4] net/mlx5: Move flow counters data
 structures from flow steering header

On Tue, Dec 4, 2018 at 6:05 PM Saeed Mahameed <saeedm@...lanox.com> wrote:
>
> After the following flow counters API refactoring:
> ("net/mlx5: Use flow counter IDs and not the wrapping cache object")
> flow counters private data structures mlx5_fc_cache and mlx5_fc are
> redundantly exposed in fs_core.h, they have nothing to do with flow
> steering core and they are private to fs_counter.c, this patch moves them
> to where they belong and reduces their exposure in the driver.
>
> Signed-off-by: Saeed Mahameed <saeedm@...lanox.com>
> ---
>  .../net/ethernet/mellanox/mlx5/core/fs_core.h | 23 -------------------
>  .../ethernet/mellanox/mlx5/core/fs_counters.c | 23 +++++++++++++++++++

The #include <linux/llist.h> can be moved together too.