On 1/8/2017 12:54 PM, Jiri Pirko wrote:
I believe that this is an e-switch requirement so it should be same for all
connected VFs, right?
yes
Sun, Jan 08, 2017 at 11:49:20AM CET, ogerl...@mellanox.com wrote:
>On 1/8/2017 12:29 PM, Jiri Pirko wrote:
>> Mon, Nov 21, 2016 at 02:05:58PM CET, sae...@mellanox.com wrote:
>> > From: Roi Dayan
>> >
>> > Some HWs need the VF driver to put part of the packet headers on the
>> > TX descriptor so t
On 1/8/2017 12:29 PM, Jiri Pirko wrote:
Mon, Nov 21, 2016 at 02:05:58PM CET, sae...@mellanox.com wrote:
From: Roi Dayan
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 abou
Mon, Nov 21, 2016 at 02:05:58PM CET, sae...@mellanox.com wrote:
>From: Roi Dayan
>
>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
mode
From: Roi Dayan
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.
The supported modes: none, link, network, transport.
Signed-off-by: Roi Dayan
Signed-off-by: Saeed Mahameed
---
include/net/devlink.h