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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4B03CC433EF for ; Tue, 17 May 2022 06:55:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=wEnisjiSlgbvDTYMnJqBgrMQGGAH5mfu3Y51dQu3D7s=; b=N1KFQh35JDwB6s ml72YrGedNCPx/Do7MwRLBsArL7LQWVcFf3N0Hm7jHMVQk9YFIHXzFgBOY8QaokAtuzh5JA4yugZ9 hgjqRcUFnIKerpqUlileB0StnCP9ybeAwzfBnuDVo66yhExsFq7r1tMsj2c/kFiqMhh3KtriLB4XO X+vUNBG98m8SYB63aSMmlwBeUInRo2vB03ohLactL1FJdT++m2rPrfFC0oBY3gNLIwjcMUCBRqrvf Y845jliGdF+qNlZjagSzmZru+ccoskzpYPUdfz2CKXzcSZmBHq+ZUCN9qUVUWFQsyZvoIn6G5vejE XG2LjpL6pw4Vu+FFROFA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nqr62-00BvES-D0; Tue, 17 May 2022 06:54:18 +0000 Received: from relay9-d.mail.gandi.net ([217.70.183.199]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nqr5r-00Bv5W-1F for linux-arm-kernel@lists.infradead.org; Tue, 17 May 2022 06:54:10 +0000 Received: (Authenticated sender: maxime.chevallier@bootlin.com) by mail.gandi.net (Postfix) with ESMTPSA id 68338FF803; Tue, 17 May 2022 06:53:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=gm1; t=1652770440; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=LSRSBOWx0X3UM1Ake1VNIh+NUfX/y6+vqtFaURfJuPo=; b=IzCag1a/2/Oiqmxyp/nm3xkf4F2qFuTTBqkI3I9j44abhdGXKoOzszw2tDuUJr0sJCgOw4 hSTRCZ2qu+jSA/YAlXPprl6h7o97SxaybLE9dlvZ7VKTjAVODeTiSAbQmiv4Lt2n7K0bqE EbaCuMIJPWevm5/Oko/dQdJvZ7G8houWWIlPT8ZZFcetvVK52nK5mapuxjpuiYMXMuDSyX +TcbKy7YOyYlJnO1PEfUkGNxqWSUuQvMSHtqzayxPzdje+U76A6hc2psOjGap3KWZd3bpj HvARvrUJ0YXO8dSpf5W49+QaLWy8JjOOaO1VMFLQ1US96DeItNdgRZ+8bJeDeQ== Date: Tue, 17 May 2022 08:53:55 +0200 From: Maxime Chevallier To: Jakub Kicinski Cc: davem@davemloft.net, Rob Herring , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, thomas.petazzoni@bootlin.com, Andrew Lunn , Florian Fainelli , Heiner Kallweit , Russell King , linux-arm-kernel@lists.infradead.org, Vladimir Oltean , Luka Perkov , Robert Marko Subject: Re: [PATCH net-next v2 2/5] net: dsa: add out-of-band tagging protocol Message-ID: <20220517085355.4fab54b3@pc-20.home> In-Reply-To: <20220516122048.70e238a2@kernel.org> References: <20220514150656.122108-1-maxime.chevallier@bootlin.com> <20220514150656.122108-3-maxime.chevallier@bootlin.com> <20220516122048.70e238a2@kernel.org> Organization: Bootlin X-Mailer: Claws Mail 4.1.0 (GTK 3.24.33; x86_64-redhat-linux-gnu) MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220516_235407_610655_56D1760E X-CRM114-Status: GOOD ( 28.31 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hello Jakub, On Mon, 16 May 2022 12:20:48 -0700 Jakub Kicinski wrote: > On Sat, 14 May 2022 17:06:53 +0200 Maxime Chevallier wrote: > > This tagging protocol is designed for the situation where the link > > between the MAC and the Switch is designed such that the Destination > > Port, which is usually embedded in some part of the Ethernet > > Header, is sent out-of-band, and isn't present at all in the > > Ethernet frame. > > > > This can happen when the MAC and Switch are tightly integrated on an > > SoC, as is the case with the Qualcomm IPQ4019 for example, where > > the DSA tag is inserted directly into the DMA descriptors. In that > > case, the MAC driver is responsible for sending the tag to the > > switch using the out-of-band medium. To do so, the MAC driver needs > > to have the information of the destination port for that skb. > > > > This out-of-band tagging protocol is using the very beggining of > > the skb headroom to store the tag. The drawback of this approch is > > that the headroom isn't initialized upon allocating it, therefore > > we have a chance that the garbage data that lies there at > > allocation time actually ressembles a valid oob tag. This is only > > problematic if we are sending/receiving traffic on the master port, > > which isn't a valid DSA use-case from the beggining. When dealing > > from traffic to/from a slave port, then the oob tag will be > > initialized properly by the tagger or the mac driver through the > > use of the dsa_oob_tag_push() call. > > > > Signed-off-by: Maxime Chevallier > > This must had been asked on v1 but there's no trace of it in the > current submission afaict... No you're correct, this wasn't explained. > If the tag is passed in the descriptor how is this not a pure > switchdev driver? The explanation must be preserved somehow. The main reason is that although the MAC and switch are rightly coupled on that platform, the switch is actually a QC8K that can live on it's own, as an external switch. Here, it's just a slightly modified version of this IP. The same goes for the MAC IP, but so far we don't support any other platform that have the MAC as a standalone controller. As far as we can tell, platforms that have this MAC also include a QCA8K, but the datasheet also mentions other modes (like outputing RGMII). Is this valid to have it as a standalone ethernet driver in that situation ? Thanks, Maxime _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel