Re: [PATCH net-next] selftests: forwarding: add Per-Stream Filtering and Policing test for Ocelot

From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Kurt Kanzenbach <kurt@linutronix.de>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
	Vinicius Costa Gomes <vinicius.gomes@intel.com>,
	Gerhard Engleder <gerhard@engleder-embedded.com>,
	"Y.B. Lu" <yangbo.lu@nxp.com>,
	Xiaoliang Yang <xiaoliang.yang_1@nxp.com>,
	Richard Cochran <richardcochran@gmail.com>,
	Yannick Vignon <yannick.vignon@nxp.com>,
	Rui Sousa <rui.sousa@nxp.com>, Jiri Pirko <jiri@nvidia.com>,
	Ido Schimmel <idosch@nvidia.com>
Subject: Re: [PATCH net-next] selftests: forwarding: add Per-Stream Filtering and Policing test for Ocelot
Date: Fri, 29 Apr 2022 16:30:47 +0200	[thread overview]
Message-ID: <Ymv2l6Un7QXjrXFy@linutronix.de> (raw)
In-Reply-To: <20220429110038.6jv76qeyjjxborez@skbuf>

On 2022-04-29 11:00:39 [+0000], Vladimir Oltean wrote:
> > I agree. Nevertheless, having a standardized tool for this kind latency
> > testing would be nice. For instance, cyclictest is also not part of the
> > kernel, but packaged for all major Linux distributions.
> 
> Right, the thing is that I'm giving myself the liberty to still make
> backwards-incompatible changes to isochron until it reaches v1.0 (right
> now it's at v0.7 + 14 patches, so v0.8 should be coming rather soon).
> I don't really want to submit unstable software for inclusion in a
> distro (plus I don't know what distros would be interested in TSN
> testing, see above).

Users of those distros, that need to test TSN, will be interested in
having it packaged rather than having it to compile first. Just make it
available, point to it in tests etc. and it should get packaged.

> And isochron itself needs to become more stable by gathering more users,
> being integrated in scripts such as selftests, catering to more varied
> requirements.
> So it's a bit of a chicken and egg situation.
If it is completely experimental then it could be added to, say,
Debian's experimental distribution so user's of unstable/sid can install
it fairly easy but it won't become part of the upcoming stable release
(the relevant freeze is currently set to 2023-02).

Sebastian