From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=jNyhd+T/9d9anCSoGKOeiOQZUa2KbCVT/Y/R829odA0=; b=kd/pME7pXs/YdCnqRxrbKWW2Gqhh4kDLHBsOyRE8A6RrQ4YCNnLEY8zQpEReVUMEL6 32d7JKq2Ik57CpKb5yj4J4ir46O6OlRuw9a6txjY/gXQebtX/JQ2Z/eK/AbTzyixQH46 9QD+WkAvH6nzjE6vnvHWZly7cMi1PYLIL5Cg7ulFOQ/R1DmyQ7nljIXBOP7c9nz+YJNT jtgmuguBRRu1PVkqPcaxNOUFMxrYm2T1yTZfFxQhsCvdrgoriH6lC2XZSuB3mHqSmAu1 QnzJHTH5fYBIaafDUTK60wUDyyHCWKcE94NDgNHr7mCrA7D3dMTAhbbDIrFeKX+W1AAO jLNw== References: <20210718214434.3938850-1-vladimir.oltean@nxp.com> <20210718214434.3938850-16-vladimir.oltean@nxp.com> From: Florian Fainelli Message-ID: <7c2b81e8-db72-4665-fe81-7254cba1e797@gmail.com> Date: Sun, 18 Jul 2021 19:47:22 -0700 MIME-Version: 1.0 In-Reply-To: <20210718214434.3938850-16-vladimir.oltean@nxp.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] [PATCH v4 net-next 15/15] net: dsa: tag_dsa: offload the bridge forwarding process List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladimir Oltean , netdev@vger.kernel.org, Jakub Kicinski , "David S. Miller" Cc: Andrew Lunn , Grygorii Strashko , Jiri Pirko , DENG Qingfang , bridge@lists.linux-foundation.org, Ido Schimmel , Nikolay Aleksandrov , Roopa Prabhu , Marek Behun , Vivien Didelot , Tobias Waldekranz On 7/18/2021 2:44 PM, Vladimir Oltean wrote: > From: Tobias Waldekranz > > Allow the DSA tagger to generate FORWARD frames for offloaded skbs > sent from a bridge that we offload, allowing the switch to handle any > frame replication that may be required. This also means that source > address learning takes place on packets sent from the CPU, meaning > that return traffic no longer needs to be flooded as unknown unicast. > > Signed-off-by: Tobias Waldekranz > Signed-off-by: Vladimir Oltean This looks pretty complicated to but if this is how it has to work, it has to. For tag_brcm.c we can simply indicate that the frame to be transmitted should have a specific bitmask of egress ports. -- Florian