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 C12C0C433FE for ; Tue, 17 May 2022 07:03:45 +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=ak2UWb9NFFw0XSbeGhU6t9MPEnOzOlNjXx15Rvh4Njc=; b=BETEyi/CFEQEkR cCGcKddFN8F0IwEEQ20l8hx5gubD7ZaW2Zv18DUN/cMK2UJtaL1wd4bOe81du95LLROiY1GbBu9jI 9GALyvQfK9Ft0ACRl4SqA8d8jumZxLUukCH/VYAmOg3B+4Vpgrr17lrzwWAk5xNulm1PCFciDAg4h q7ZKjH5HXGbIdE0DCxtGIj+ehcOmh6d01nYItdDATJk1ETjrP/zoUSNjN8lqVQ2ko5rD0u/UfIox7 0Q2E6lUJ6+8CiAJs0k/saa+ihI7T7Az3uuNPSxOfoo34dNVnrK3zxS1Ue6t42nfke/48KJQmiRumD Z5XU6FhCxtU+JfD/CvoQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nqrDm-00By4q-9c; Tue, 17 May 2022 07:02:19 +0000 Received: from relay11.mail.gandi.net ([217.70.178.231]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nqrDZ-00Bxz2-7q for linux-arm-kernel@lists.infradead.org; Tue, 17 May 2022 07:02:07 +0000 Received: (Authenticated sender: maxime.chevallier@bootlin.com) by mail.gandi.net (Postfix) with ESMTPSA id A1ADA10000B; Tue, 17 May 2022 07:01:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=gm1; t=1652770920; 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=9KazaW1SkFx7SybTXPFRmtUBoimvEisxPHGbF+BGpFc=; b=R5CTzLA4Ubtz8fYfQ2SDt3yt3caIj3yrtuf0wjEBNuwsMPcn30DzUr5KYbk4TNHmWe5fGn PceQ1IHai4j++s5NU/WJqjbOkn2Legv9KSeORmjtH8o9pkGx3aFTRfx+W7+ZT9URZnolio rdvxiV4rfaQVB4ISVYv/iuthulsjxDhJH3SrSqohMvKj6qwxjd0LAicq3OjeHg35EOYnlx n46ipD/l/baalEMoG1wmOkd/dNPzNzBChI9l0XUYPajQTBeBpIpPdUb3AhJZpwaMbDJqQa h3H3Vpkf1+E6oKnbD4wWfESDyqbNcBgFMRC22ANt+DxSQlDY99MkW97sHrc7qQ== Date: Tue, 17 May 2022 09:01:56 +0200 From: Maxime Chevallier To: Vladimir Oltean 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" , Luka Perkov , Robert Marko Subject: Re: [PATCH net-next v2 2/5] net: dsa: add out-of-band tagging protocol Message-ID: <20220517090156.3fde5a8f@pc-20.home> In-Reply-To: <20220514224002.vvmd43lnjkbsw2g3@skbuf> References: <20220514150656.122108-1-maxime.chevallier@bootlin.com> <20220514150656.122108-3-maxime.chevallier@bootlin.com> <20220514224002.vvmd43lnjkbsw2g3@skbuf> 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-20220517_000205_617892_94C95C93 X-CRM114-Status: GOOD ( 31.86 ) 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 Hi Vlad, On Sat, 14 May 2022 22:40:03 +0000 Vladimir Oltean wrote: > On Sat, May 14, 2022 at 05:06:53PM +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 > > --- > > Why put the DSA pseudo-header at skb->head rather than push it using > skb_push()? I thought you were going to check for the presence of a > DSA header using something like skb->mac_len == ETH_HLEN + tag len, > but right now it sounds like treating garbage in the headroom as a > valid DSA tag is indeed a potential problem. If you can't sort that > out using information from the header offsets alone, maybe an skb > extension is required? Indeed, I thought of that, the main reason is that pushing/poping in itself is not enough, you also have to move the whole mac_header to leave room for the tag, and then re-set it in it's original location. There's nothing wrong with this, but it looked a bit cumbersome just to insert a dummy tag that gets removed rightaway. Does that make sense ? But yes I would really like to get a way to know wether the tag is there or not, I'll dig a bit more to see if I can find a way to get this info from the various skb offsets in a reliable way. Thanks, Maxime _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel