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  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:   Tue, 03 Dec 2019 09:22:55 -0800
From:   Vinicius Costa Gomes <>
To:     Ivan Khoronzhuk <>,
        Jose Abreu <>
Cc:     "netdev\" <>,
        Joao Pinto <>,
        Jesus Sanchez-Palencia <>,
        Vladimir Oltean <>
Subject: Re: tperf: An initial TSN Performance Utility


Ivan Khoronzhuk <> writes:

> On Tue, Dec 03, 2019 at 10:00:15AM +0000, Jose Abreu wrote:
>>Hi netdev,
>>[ I added in cc the people I know that work with TSN stuff, please add
>>anyone interested ]
>>We are currently using a very basic tool for monitoring the CBS
>>performance of Synopsys-based NICs which we called tperf. This was based
>>on a patchset submitted by Jesus back in 2017 so credits to him and
>>blames on me :)
>>The current version tries to send "dummy" AVTP packets, and measures the
>>bandwidth of both receiver and sender. By using this tool in conjunction
>>with iperf3 we can check if CBS reserved queues are behaving correctly
>>by reserving the priority traffic for AVTP packets.
>>You can checkout the tool in the following address:
>>	GitHub:
>>We are open to improve this to more robust scenarios, so that we can
>>have a common tool for TSN testing that's at the same time light
>>weighted and precise.
>>Anyone interested in helping ?

@Jose, that's really nice. I will play with it for sure.

> I've also have tool that already includes similar functionality.
> It's also about from 2016-2017 years.
> Not ideal, but it helped me a lot for last years. Also worked with XDP, but
> libbpf library is old already and should be updated. But mostly it was used to
> get latencies and observe hw ts how packets are put on the line.
> I've used it for CBS and for TAPRIO scheudler testing, observing h/w ts of each
> packet, closed and open gates, but a target board should support hw ts to be
> accurate, that's why ptp packets were used.
> It includes also latency measurements based as on hw timestamp as on software
> ts.

@Ivan, I took a look at plget some time ago. One thing that I missed is
a test method that doesn't use the HW transmit timestamp, as retrieving
the TX timestamp can be quite slow, and makes it hard to measure latency
when sending something like ~10K packet/s.

What I mean is something like this: the transmit side takes a timestamp,
stores it in the packet being sent and sends the packet, the receive
side gets the HW receive timestamp (usually faster) and calculates the
latency based on the HW receive timestamp and the timestamp in the
packet. I know that you should take the propagation delay and other
stuff into account. But on back-to-back systems (at least) these other
delays should be quite small compared to the whole latency.

Do you think adding a test method similar to this would make sense for


Powered by blists - more mailing lists