From: Jose Abreu <Jose.Abreu@synopsys.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: Joao Pinto <Joao.Pinto@synopsys.com>,
Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Vladimir Oltean <olteanv@gmail.com>
Subject: tperf: An initial TSN Performance Utility
Date: Tue, 3 Dec 2019 10:00:15 +0000 [thread overview]
Message-ID: <BN8PR12MB3266E99E5C289CB6B77A5C58D3420@BN8PR12MB3266.namprd12.prod.outlook.com> (raw)
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: https://github.com/joabreu/tperf
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 ?
---
Thanks,
Jose Miguel Abreu
next reply other threads:[~2019-12-03 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 10:00 Jose Abreu [this message]
2019-12-03 10:10 ` tperf: An initial TSN Performance Utility Vladimir Oltean
2019-12-03 10:29 ` Jose Abreu
2019-12-03 14:27 ` Ivan Khoronzhuk
2019-12-03 17:22 ` Vinicius Costa Gomes
2019-12-03 19:05 ` Ivan Khoronzhuk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BN8PR12MB3266E99E5C289CB6B77A5C58D3420@BN8PR12MB3266.namprd12.prod.outlook.com \
--to=jose.abreu@synopsys.com \
--cc=Joao.Pinto@synopsys.com \
--cc=jesus.sanchez-palencia@intel.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vinicius.gomes@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).