From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.0 required=3.0 tests=DATE_IN_PAST_06_12, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1036CC04AB4 for ; Sun, 19 May 2019 18:44:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id CBA0F20578 for ; Sun, 19 May 2019 18:44:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="Fx8pX7dN" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727007AbfESSow (ORCPT ); Sun, 19 May 2019 14:44:52 -0400 Received: from mail-yw1-f67.google.com ([209.85.161.67]:46360 "EHLO mail-yw1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726074AbfESSow (ORCPT ); Sun, 19 May 2019 14:44:52 -0400 Received: by mail-yw1-f67.google.com with SMTP id a130so4932095ywe.13 for ; Sun, 19 May 2019 11:44:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RDPtq1zhnEX4awgYpuSSAKr7uq74Q/mnHFav4e1VSNQ=; b=Fx8pX7dNBRju6fhB4eAHfXxIpZj2UIhgTL0B/H2VkDfksr1OT7ahQJotnt8zcXaKJN OrPgC2zeGtYRSZf4FVWd56LYeabrvAXDbxjXPGt++BaB2Cpq4AmfEy571qjOR71PLHZS ZkIGGPGrOtacIuCAMrAxeBIr/GD7lv7maHRhWWWWrzs9CLUyJBvu+E9GcMj6TYnwxVlF Ko1L8SrHPjuPQCIGPZ8AgwMMEygvhHh293kxbXHcBA3a4xluaeYnp2A51yrUBnWzV27C sdjqPb0tuUK8Jj/C00yIU/fCSSFw3GOIKoGLuaknv3hBMxu8RIYQIyEn2u6PmvO512z2 6e9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RDPtq1zhnEX4awgYpuSSAKr7uq74Q/mnHFav4e1VSNQ=; b=rPIes8dKjadF02qEQd1RHxdXvO7W+3FkyhpeZoZn4aHJWHoglfxxRxwyAs3w2bqYQU XmiDbO304DmCL9caCfIlLwmLr7cXi6IYV59utiuJcF3TOKorONfL/FBAhsVajnldke7C z0vnU+wxSekWB8kcBBS2BkCWNU8KyZwe7YTu0fW2h+IfRdY0R72Ox2ND6zPeC+GGfrJ0 ftekzWBFKPTI0H0aXsdLDMwEmIHSZFx4ADm6QZhXY5ChQorHnQDa1Jni8n8YRZRgm5ep Isa5CpfawRtfxW/xjkHb/NNfEB+wvT0pKDQtDWTRxzjiXvYVcKBeVIjdQXAIf7cNkrde VOfQ== X-Gm-Message-State: APjAAAWKoT7XVrbtk0i2gIHYZKv3RSmJtwqh/TdvwYUKfU7l1KGvF4QU V6YXrazHUhhArPEwr7g0UV4U406ClLPdXccvxn0tT5M8lxc= X-Google-Smtp-Source: APXvYqwartGeASgta1G791iJh55lRKRvPgrV4NsKGSlaG/6fsMMN/ulEgxafR12KffEwIDfntjTbppDNLfxQYUT3Ceg= X-Received: by 2002:a81:91d7:: with SMTP id i206mr14666641ywg.147.1558250628692; Sun, 19 May 2019 00:23:48 -0700 (PDT) MIME-Version: 1.0 References: <1558084668-21203-1-git-send-email-wenxu@ucloud.cn> In-Reply-To: <1558084668-21203-1-git-send-email-wenxu@ucloud.cn> From: Or Gerlitz Date: Sun, 19 May 2019 10:23:37 +0300 Message-ID: Subject: Re: [PATCH v2] net/mlx5e: Add bonding device for indr block to offload the packet received from bonding device To: wenxu@ucloud.cn Cc: Saeed Mahameed , Roi Dayan , Linux Netdev List Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Fri, May 17, 2019 at 12:45 PM wrote: > From: wenxu > > 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