From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Murali Karicheri <m-karicheri2@ti.com>, netdev@vger.kernel.org
Subject: Re: TSN: taprio scheduler
Date: Tue, 26 Mar 2019 14:02:43 -0700 [thread overview]
Message-ID: <87sgv9e4cs.fsf@intel.com> (raw)
In-Reply-To: <94a8e924-028c-46f5-e842-9e4e0b2db5d3@ti.com>
Hi Murali,
Murali Karicheri <m-karicheri2@ti.com> writes:
> Hi Vinicius,
>
> My name is Murali Karicheri from Texas Instruments Ltd. We have
> AM65x/DRA80xMProcessor, that is capable of supporting TSN. Our solution
> would use the ICSSG_PRU which is a fully programmable industrial
> communication subsystems to enable future-proof designs for customers
> that need to adopt the new Gigabit Time-sensitive
> Networks(TSN)standards. More details can be seen in the TRM at
> http://www.ti.com/lit/ug/spruid7c/spruid7c.pdf
>
Really glad to see more people interested in TSN. Will take a look at
that datasheet to see if the interface I will propose will turn to be
too awkward for those devices.
> I am part of the team that is working to implement IEEE Std 802.1Qbv
> scheduler (Time aware Shaper) with Frame pre-emption capabilities in a
> RT Linux based solution. I saw your commit for taprio which adds basic
> support in Linux and is a good starting point for me.
>
> commit 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22
> Author: Vinicius Costa Gomes <vinicius.gomes@intel.com>
> Date: Fri Sep 28 17:59:43 2018 -0700
>
> tc: Add support for configuring the taprio scheduler
>
> Also went through https://lwn.net/Articles/767383/
>
> Basically wondering what is the current status of the following under
> "Future work" in the above link and also to explore if we could
> collaborate on developing missing pieces.
>
> ===== from https://lwn.net/Articles/767383/ =======================
> - Add support for multiple schedules, so something like the Admin
> and Oper schedules from IEEE 802.1Q-2018 can be implemented,
> probably "cycle-time" will be re-implemented at this time;
>
> - Add support for HW offloading;
>
> - Add support for Frame Preemption related commands (formerly
> 802.1Qbu, now part of 802.1Q);
> ======================================================================
The series that I planning to send this week has some ideas about how to
solve all these three points. But for hardware offloading and frame
preemption, all I will propose is the interface for talking to the
driver.
>
> To begin with I am currently exploring how to test this software
> implementation of taprio and what are all the dependencies.
>
> Do I need multi-q support in the Ethernet driver to test taprio? Looks
> like it is needed. What else is needed to test this feature? If you have
> any additional patches that you have tested, that would help for my
> initial ramp.
Yes, for now, the only requirement is a multiqueue device. And thinking
a little more, even that may be lifted for the software only mode, with
some work.
About testing, to make things easier to test we grouped some READMEs and
scripts in this gist, perhaps it can help you on your experiments:
https://gist.github.com/jeez/bd3afeff081ba64a695008dd8215866f
See if helps.
Cheers,
--
Vinicius
next prev parent reply other threads:[~2019-03-26 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 20:30 TSN: taprio scheduler Murali Karicheri
2019-03-26 21:02 ` Vinicius Costa Gomes [this message]
2019-03-27 19:29 ` Murali Karicheri
2019-04-17 7:55 ` Jose Abreu
2019-04-17 15:57 ` Vinicius Costa Gomes
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=87sgv9e4cs.fsf@intel.com \
--to=vinicius.gomes@intel.com \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
/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).