From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: [PATCH mlx5-next v1 2/8] net/mlx5: Add support for flow table destination number Date: Fri, 13 Jul 2018 00:51:10 +0300 Message-ID: References: <20180711111045.6282-1-leon@kernel.org> <20180711111045.6282-3-leon@kernel.org> <20180712212618.GS30390@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20180712212618.GS30390@mellanox.com> Sender: netdev-owner@vger.kernel.org To: Jason Gunthorpe Cc: Yishai Hadas , Doug Ledford , Leon Romanovsky , RDMA mailing list , Saeed Mahameed , linux-netdev List-Id: linux-rdma@vger.kernel.org On Fri, Jul 13, 2018 at 12:26 AM, Jason Gunthorpe wrote: > On Fri, Jul 13, 2018 at 12:00:41AM +0300, Or Gerlitz wrote: >> On Wed, Jul 11, 2018 at 2:10 PM, Leon Romanovsky wrote: >> > From: Yishai Hadas >> > >> > Add support to set a destination from a flow table number. >> > This functionality will be used in downstream patches from this >> > series by the DEVX stuff. >> >> Reading your cover letter, I still don't understand what is missing >> in the current mlx5 fs core API for your needs. After all, you do >> create flow tables from the IB driver through fs core calls, right? >> so @ the end of the day, you have the FT pointer to provide the >> core, why you need the FT number? > > Via the devx API userspace can create flow tables directly without > going to the driver's flow steering core. so why you change the core?