From: Vladimir Oltean <olteanv@gmail.com>
To: Jose Abreu <Jose.Abreu@synopsys.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Joao Pinto <Joao.Pinto@synopsys.com>,
Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Po Liu <po.liu@nxp.com>,
Xiaoliang Yang <xiaoliang.yang_1@nxp.com>
Subject: Re: tperf: An initial TSN Performance Utility
Date: Tue, 3 Dec 2019 12:10:54 +0200 [thread overview]
Message-ID: <CA+h21hpTLOtjobFjGt5dzJ+nZvLjAMfCO+_-3OCCAaSE1yMSfQ@mail.gmail.com> (raw)
In-Reply-To: <BN8PR12MB3266E99E5C289CB6B77A5C58D3420@BN8PR12MB3266.namprd12.prod.outlook.com>
Hi Jose,
On Tue, 3 Dec 2019 at 12:00, Jose Abreu <Jose.Abreu@synopsys.com> 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: 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
Sounds nice, I'm interested in giving this a try on the LS1028A ENETC.
Do you have any more tooling around tperf? Does the talker advertise
the stream in such a way that a switch could reserve bandwidth too?
Do you plan to add this to the kernel tree (e.g.
tools/testing/selftests/tsn or such) or how do you want to maintain
this long-term?
I've added more people from NXP who may also be interested.
Thanks,
-Vladimir
next prev parent reply other threads:[~2019-12-03 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 10:00 tperf: An initial TSN Performance Utility Jose Abreu
2019-12-03 10:10 ` Vladimir Oltean [this message]
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=CA+h21hpTLOtjobFjGt5dzJ+nZvLjAMfCO+_-3OCCAaSE1yMSfQ@mail.gmail.com \
--to=olteanv@gmail.com \
--cc=Joao.Pinto@synopsys.com \
--cc=Jose.Abreu@synopsys.com \
--cc=jesus.sanchez-palencia@intel.com \
--cc=netdev@vger.kernel.org \
--cc=po.liu@nxp.com \
--cc=vinicius.gomes@intel.com \
--cc=xiaoliang.yang_1@nxp.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).