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=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_2 autolearn=no 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 879EEC3A5A1 for ; Sun, 25 Aug 2019 07:13:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 304F220850 for ; Sun, 25 Aug 2019 07:13:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=nic.cz header.i=@nic.cz header.b="gOIHz3q1" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726731AbfHYHNk (ORCPT ); Sun, 25 Aug 2019 03:13:40 -0400 Received: from mail.nic.cz ([217.31.204.67]:45138 "EHLO mail.nic.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726159AbfHYHNj (ORCPT ); Sun, 25 Aug 2019 03:13:39 -0400 Received: from localhost (unknown [172.20.6.135]) by mail.nic.cz (Postfix) with ESMTPSA id 1CAD8140BAD; Sun, 25 Aug 2019 09:13:38 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1566717218; bh=A3hNoVN5ZlaSFUIFfnPziJkqklzql/UhWKIJNmnGCYo=; h=Date:From:To; b=gOIHz3q1uerFDWFjmHI8DGJK6xySVHSF/1uNszaXc6sp48ISxlOoZsXHPeg9sxAta 2+DzfNYLZWv9zfjoi4ymdf6e81rJKjesda35h1f3bXQpnltcp4Ao1pDzzRo9zuj7p5 UwoWiQj95ieZb9h8/tW+mJ1tBT3erXIAXhN2jEdY= Date: Sun, 25 Aug 2019 09:13:37 +0200 From: Marek Behun To: Florian Fainelli Cc: netdev@vger.kernel.org, Andrew Lunn , Vivien Didelot , David Ahern , Stephen Hemminger , Chris Healy , Vladimir Oltean Subject: Re: [PATCH RFC net-next 0/3] Multi-CPU DSA support Message-ID: <20190825091337.236ee73a@nic.cz> In-Reply-To: References: <20190824024251.4542-1-marek.behun@nic.cz> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.100.3 at mail.nic.cz X-Virus-Status: Clean Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Sat, 24 Aug 2019 13:04:04 -0700 Florian Fainelli wrote: > Now, the 4.9 kernel behavior actually works just fine because eth1 is > not a special interface, so no tagging is expected, and "wifi", although > it supports DSA tagging, represents another side of the CPU/host network > stack, so you never have to inject frames into the switch, because you > can use eth1 to do that and let MAC learning do its job to forward to > the correct port of the switch. Hi Florian, Sorry, I am having trouble understanding what you mean in the paragraph I quoted above (and paragraphs afterwards). eth0 and eth1 are interfaces created by an ethernet driver. wlan0 is an interface created by wireless driver. wifi is a slave interface created by DSA for port 5 on the switch. eth1 is DSA slave or a DSA master connected to port 5? How does DSA handle two interfaces with same reg property? Marek