Received: by 2002:a05:6a10:d5a5:0:0:0:0 with SMTP id gn37csp1578605pxb; Fri, 1 Oct 2021 13:57:33 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzW/GjF4zbPnFDKo0OUup2dpsiDPD3trT5PD78MKLEjue/f+PC8+rlSqCKksUwPF6W+flVZ X-Received: by 2002:a05:6402:34d2:: with SMTP id w18mr246632edc.222.1633121853408; Fri, 01 Oct 2021 13:57:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1633121853; cv=none; d=google.com; s=arc-20160816; b=Fm6oYRWGJL2aOvqdL6brzQN31aGPzdf5GCm61AYboYJQjkaIxVFV4UoKF7ccoNWSxZ tUh0ydGGlYq+Mi3jye6NMaMFmnSW1r+HyO5HkMsN8/HCP4pRC3iifoL0HA+65htws2sx FeXOmBWV1OH1ypAvRoj6pX8/KOp/8HGRuQJhBKdnS7Q/ztqIgDKxV0ngl2DtBK0MO2NK s70A9jkCJ/5tElgGri3d/mPAbP5Xarcmi5OPUrMB/2ls9whoKfiRPLb6roZ8oX0hO2lq 0K2SHt23+/IVfFJ0dLll9E9mq7q9oXF/qMsqMV8Jn3k3Aya8zY+LE9Vlk0eB/YJQOwye 39hA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=Cug9eI3B2zkJPE6pZCcN90lHzJr2K/HsnEKZZEtuMIs=; b=xtnwQ3saP3TPigzpsvFzbZ0i4e+JrII5MORoDEDzjJx+U0UwNn9yzJiESJpSmYKeF2 lLwhuXVvXvVyBWBSXEzc9SrV86+KjpKDA2ir1l5bcltSf1vHvaa+qY1XHehIvty011/y ya4QjvVs8UiLEahnPRkWeqg78BpHTDrpldB3eFf0JTCqEy8F6EI75bZl+e62Sn82z7yy +OOvgII4Jbi121NJfc5raPrBsDmWyQhOQZaRTtufdV9If/ey1M/jZvv29YQCTpmZcABs 0IIFivAkPTQPQPidfFk8EXtp1UK5iZ1X4fkony1ChQKNysYewEJa2KBdjPdKH98GZvUn x2hA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v14si8160773edb.187.2021.10.01.13.57.07; Fri, 01 Oct 2021 13:57:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1355317AbhJAR27 (ORCPT + 99 others); Fri, 1 Oct 2021 13:28:59 -0400 Received: from mga05.intel.com ([192.55.52.43]:50616 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1355262AbhJAR26 (ORCPT ); Fri, 1 Oct 2021 13:28:58 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10124"; a="311051743" X-IronPort-AV: E=Sophos;i="5.85,339,1624345200"; d="scan'208";a="311051743" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Oct 2021 10:27:14 -0700 X-IronPort-AV: E=Sophos;i="5.85,339,1624345200"; d="scan'208";a="521239016" Received: from unknown (HELO vcostago-mobl3) ([10.134.46.83]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Oct 2021 10:27:12 -0700 From: Vinicius Costa Gomes To: Xiaoliang Yang , "davem@davemloft.net" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" Cc: "Arvid.Brodin@xdin.com" , "m-karicheri2@ti.com" , "michael.chan@broadcom.com" , "vishal@chelsio.com" , "saeedm@mellanox.com" , "jiri@mellanox.com" , "idosch@mellanox.com" , "alexandre.belloni@bootlin.com" , "ivan.khoronzhuk@linaro.org" , "andre.guedes@linux.intel.com" , "allan.nielsen@microchip.com" , "joergen.andreasen@microchip.com" , Vladimir Oltean , "jhs@mojatatu.com" Subject: RE: [EXT] Re: [RFC, net-next] net: qos: introduce a frer action to implement 802.1CB In-Reply-To: References: <20210928114451.24956-1-xiaoliang.yang_1@nxp.com> <87czos9vnj.fsf@linux.intel.com> Date: Fri, 01 Oct 2021 10:27:12 -0700 Message-ID: <87lf3cfyfj.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Xiaoliang Yang writes: > Hi Vinicius, > > On Sep 29, 2021 at 6:35:59 +0000, Vinicius Costa Gomes wrote: >> > This patch introduce a frer action to implement frame replication and >> > elimination for reliability, which is defined in IEEE P802.1CB. >> > >> >> An action seems, to me, a bit too limiting/fine grained for a frame replication >> and elimination feature. >> >> At least I want to hear the reasons that the current hsr/prp support cannot be >> extended to support one more tag format/protocol. >> >> And the current name for the spec is IEEE 802.1CB-2017. >> > 802.1CB can be set on bridge ports, and need to use bridge forward > Function as a relay system. It only works on identified streams, > unrecognized flows still need to pass through the bridged network > normally. This ("only on identified streams") is the strongest argument so far to have FRER also as an action, in adition to the current hsr netdevice approach. > > But current hsr/prp seems only support two ports, and cannot use the > ports in bridge. It's hard to implement FRER functions on current HSR > driver. That the hsr netdevice only support two ports, I think is more a bug than a design issue. Which will need to get fixed at some point. Speaking of functions, one thing that might be interesting is trying to see if it makes sense to make part of the current hsr functionality a "library" so it can be used by tc-frer as well. (less duplication of bugs). > > You can see chapter "D.2 Example 2: Various stack positions" in IEEE 802.1CB-2017, > Protocol stack for relay system is like follows: > > Stream Transfer Function > | | > | Sequence generation > | Sequence encode/decode > Stream identification Active Stream identification > | | > | Internal LAN---- Relay system forwarding > | | | > MAC MAC MAC > > Use port actions to easily implement FRER tag add/delete, split, and > recover functions. > > Current HSR/PRP driver can be used for port HSR/PRP set, and tc-frer > Action to be used for stream RTAG/HSR/PRP set and recover. I am still reading the spec and trying to imagine how things would fit together: - for which use cases tc-frer would be useful; - for which use cases the hsr netdevice would be useful; - would it make sense to have them in the same system? > > Thanks, > Xiaoliang Cheers, -- Vinicius