[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <85cb3c37-a9e3-97cf-eb21-faab8f04c334@dev.mellanox.co.il>
Date: Sun, 15 Jul 2018 11:26:52 +0300
From: Yishai Hadas <yishaih@....mellanox.co.il>
To: Or Gerlitz <gerlitz.or@...il.com>
Cc: Yishai Hadas <yishaih@...lanox.com>,
Doug Ledford <dledford@...hat.com>,
Jason Gunthorpe <jgg@...lanox.com>,
Leon Romanovsky <leonro@...lanox.com>,
RDMA mailing list <linux-rdma@...r.kernel.org>,
Saeed Mahameed <saeedm@...lanox.com>,
linux-netdev <netdev@...r.kernel.org>,
Majd Dibbiny <majd@...lanox.com>
Subject: Re: [PATCH mlx5-next v1 1/8] net/mlx5: Add forward compatible support
for the FTE match data
On 7/15/2018 11:03 AM, Or Gerlitz wrote:
> On Sun, Jul 15, 2018 at 10:26 AM, Yishai Hadas
> <yishaih@....mellanox.co.il> wrote:
>> On 7/12/2018 11:53 PM, Or Gerlitz wrote:
>>> On Wed, Jul 11, 2018 at 2:10 PM, Leon Romanovsky <leon@...nel.org> wrote:
>>>> From: Yishai Hadas <yishaih@...lanox.com>
>
>>>> Use the PRM size including the reserved when working with the FTE
>>>> match data.
>
> -- we need a clear memo as part of your change-logs and/or cover-letter/s that
> explains the overall approach/design for
> doing-things-without-changing-the-kernel,
> does this exist?
Yes, the DEVX series that was previously accepted clearly stated that
this is its target as part of its cover-letter [1]. This motivation
appears also as part of this specific commit log.
From the cover letter:
"The main purpose here is to make the user space driver as independent
as possible from the kernel so that future device functionality and
commands can be activated with minimal to none kernel changes.
[1]
https://patchwork.ozlabs.org/cover/930449/
Powered by blists - more mailing lists