lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 29 Apr 2022 16:30:47 +0200
From:   Sebastian Andrzej Siewior <>
To:     Vladimir Oltean <>
Cc:     Kurt Kanzenbach <>,
        "" <>,
        Jakub Kicinski <>,
        "David S. Miller" <>,
        Paolo Abeni <>,
        Eric Dumazet <>,
        Florian Fainelli <>,
        Vivien Didelot <>,
        Andrew Lunn <>,
        Claudiu Manoil <>,
        Alexandre Belloni <>,
        "" <>,
        Vinicius Costa Gomes <>,
        Gerhard Engleder <>,
        "Y.B. Lu" <>,
        Xiaoliang Yang <>,
        Richard Cochran <>,
        Yannick Vignon <>,
        Rui Sousa <>, Jiri Pirko <>,
        Ido Schimmel <>
Subject: Re: [PATCH net-next] selftests: forwarding: add Per-Stream Filtering
 and Policing test for Ocelot

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).


Powered by blists - more mailing lists