[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <29c008d0437571d4ce358ffdf5d3530ca8fce23c.camel@mellanox.com>
Date: Wed, 5 Dec 2018 22:26:26 +0000
From: Saeed Mahameed <saeedm@...lanox.com>
To: "xiyou.wangcong@...il.com" <xiyou.wangcong@...il.com>
CC: Jason Gunthorpe <jgg@...lanox.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Leon Romanovsky <leonro@...lanox.com>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>
Subject: Re: [PATCH mlx5-next 4/4] net/mlx5: Move flow counters data
structures from flow steering header
On Tue, 2018-12-04 at 21:04 -0800, Cong Wang wrote:
> 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.
sure will do that in V2
thanks Cong!
Powered by blists - more mailing lists