netdev - Re: [PATCH v2] net/mlx5e: Add bonding device for indr block to offload the packet received from bonding device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJ3xEMikS1gNpkTkX1fmQD6GFJutg1qzU_-3dgQA57u0Z09iGg@mail.gmail.com>
Date:   Sun, 19 May 2019 10:23:37 +0300
From:   Or Gerlitz <gerlitz.or@...il.com>
To:     wenxu@...oud.cn
Cc:     Saeed Mahameed <saeedm@...lanox.com>,
        Roi Dayan <roid@...lanox.com>,
        Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: [PATCH v2] net/mlx5e: Add bonding device for indr block to
 offload the packet received from bonding device

On Fri, May 17, 2019 at 12:45 PM <wenxu@...oud.cn> wrote:
> From: wenxu <wenxu@...oud.cn>
>
> The mlx5e support the lag mode. When add mlx_p0 and mlx_p1 to bond0.
> packet received from mlx_p0 or mlx_p1 and in the ingress tc flower
> forward to vf0. The tc rule can't be offloaded because there is
> no indr_register_block for the bonding device.

For the bonding case, the offloading strategy is tc block sharing,
namly have user-space
share the tc block of the upper device (bond) with the lower devices
(mlx5 p0 and p1).

This is implemented for example in ovs.

You can read on tc block sharing in the mlxsw driver wiki [1]

Or.

[1] https://github.com/Mellanox/mlxsw/wiki/ACLs#shared-blocks-support