[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7e783e5c-a4e1-bdc9-e5bb-73762f05ad19@nvidia.com>
Date: Sun, 22 Nov 2020 17:17:12 +0200
From: Aya Levin <ayal@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>,
Saeed Mahameed <saeedm@...dia.com>
CC: Leon Romanovsky <leonro@...lanox.com>, <netdev@...r.kernel.org>,
<linux-rdma@...r.kernel.org>, Moshe Shemesh <moshe@...dia.com>
Subject: Re: [PATCH mlx5-next 09/16] net/mlx5: Expose IP-in-IP TX and RX
capability bits
On 11/22/2020 1:58 AM, Jakub Kicinski wrote:
> On Fri, 20 Nov 2020 15:03:32 -0800 Saeed Mahameed wrote:
>> From: Aya Levin <ayal@...dia.com>
>>
>> Expose FW indication that it supports stateless offloads for IP over IP
>> tunneled packets per direction. In some HW like ConnectX-4 IP-in-IP
>> support is not symmetric, it supports steering on the inner header but
>> it doesn't TX-Checksum and TSO. Add IP-in-IP capability per direction to
>> cover this case as well.
>
> What's the use for the rx capability in Linux? We don't have an API to
> configure that AFAIK.
>
Correct, the rx capability bit is used by the driver to allow flow
steering on the inner header.
Powered by blists - more mailing lists