From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <netdev-owner@vger.kernel.org>
Received: from mail-qt0-f172.google.com ([209.85.216.172]:44955 "EHLO
        mail-qt0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932218AbeCFAQR (ORCPT
        <rfc822;netdev@vger.kernel.org>); Mon, 5 Mar 2018 19:16:17 -0500
Received: by mail-qt0-f172.google.com with SMTP id g60so22593059qtd.11
        for <netdev@vger.kernel.org>; Mon, 05 Mar 2018 16:16:17 -0800 (PST)
Date: Mon, 5 Mar 2018 16:16:13 -0800
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: John Hurley <john.hurley@netronome.com>
Cc: Or Gerlitz <gerlitz.or@gmail.com>,
        Linux Netdev List <netdev@vger.kernel.org>,
        Jiri Pirko <jiri@mellanox.com>,
        Or Gerlitz <ogerlitz@mellanox.com>,
        Simon Horman <simon.horman@netronome.com>
Subject: Re: [RFC net-next 0/6] offload linux bonding tc ingress rules
Message-ID: <20180305161613.2a692833@cakuba.netronome.com>
In-Reply-To: <CAK+XE=nSQQ5NY2iY9CnFDmb8FLRsR81AR0+tqGScO0Nngo=w7g@mail.gmail.com>
References: <1520256514-27885-1-git-send-email-john.hurley@netronome.com>
        <CAJ3xEMjzv_HkXvr11xKNFKETY_f0DhTx2m6AbdMBf5x6EfEUVg@mail.gmail.com>
        <CAK+XE=nSQQ5NY2iY9CnFDmb8FLRsR81AR0+tqGScO0Nngo=w7g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On Mon, 5 Mar 2018 23:57:18 +0000, John Hurley wrote:
> > what is your approach for rules whose bond is their egress device
> > (ingress = vf port
> > representor)?  
> 
> Egress offload will be handled entirely by the NFP driver.
> Basically, notifiers will track the slaves/masters and update the card
> with any groups that consist entirely of reprs.
> We then offload the TC rule outputting to the given group - because it
> is an ingress match we can access the egress netdev in the block
> callback.

And you handle egdev call too?  Or are we hoping to get rid of that
before? :)