[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <90f3f9f5-beec-be9d-7c92-e6f41f3fd55e@mellanox.com>
Date: Sun, 8 Jan 2017 12:49:20 +0200
From: Or Gerlitz <ogerlitz@...lanox.com>
To: Jiri Pirko <jiri@...nulli.us>
CC: Saeed Mahameed <saeedm@...lanox.com>,
"David S. Miller" <davem@...emloft.net>, <netdev@...r.kernel.org>,
Roi Dayan <roid@...lanox.com>
Subject: Re: [PATCH net-next 4/7] devlink: Add E-Switch inline mode control
On 1/8/2017 12:29 PM, Jiri Pirko wrote:
> Mon, Nov 21, 2016 at 02:05:58PM CET, saeedm@...lanox.com wrote:
>> From: Roi Dayan <roid@...lanox.com>
>>
>> Some HWs need the VF driver to put part of the packet headers on the
>> TX descriptor so the e-switch can do proper matching and steering.
> Could you please elaborate a bit about possible use-cases for different
> modes? Thanks.
As written in the change log, some HW models have this requirement that
the header set you want eswitch matching on (e.g L2/L3) is present as MD
on the xmit DMA descriptor.
To address these requirements, following the admin devlink directive the
FW advertizes that
to the VF, they are doing so in their xmit logic and the host driver
enforces that the VF has the proper inline mode before we are willing to
offload eswitch matching rules. If the VF doesn't obey to the
requirement the packets are dropped by HW.
Or.
Or.
Powered by blists - more mailing lists