Re: [RFC iproute2-next v1 5/5] tc: Add support for configuring the taprio scheduler

2018-07-24 Thread Vinicius Costa Gomes
Hi, Vinicius Costa Gomes writes: > Hi, > > Stephen Hemminger writes: > [...] >> >> Why not just use batch mode? Introducing another input mode in tc that is >> only in one qdisc seems like a bad idea. > > Seems that I have missed batch mode. I am going to play with it a little > and see how t

Re: [RFC iproute2-next v1 5/5] tc: Add support for configuring the taprio scheduler

2018-07-17 Thread Vinicius Costa Gomes
Hi, Stephen Hemminger writes: > On Fri, 13 Jul 2018 17:06:11 -0700 > Vinicius Costa Gomes wrote: > >> +while (fscanf(f, "%ms %x %" PRIu32 "\n", &cmd_str, &gatemask, >> &interval) != EOF) { >> +struct rtattr *entry; >> + >> +err = str_to_entry_cmd(cmd_str); >> +

Re: [RFC iproute2-next v1 5/5] tc: Add support for configuring the taprio scheduler

2018-07-14 Thread Stephen Hemminger
On Fri, 13 Jul 2018 17:06:11 -0700 Vinicius Costa Gomes wrote: > + while (fscanf(f, "%ms %x %" PRIu32 "\n", &cmd_str, &gatemask, > &interval) != EOF) { > + struct rtattr *entry; > + > + err = str_to_entry_cmd(cmd_str); > + free(cmd_str); > + > +

[RFC iproute2-next v1 5/5] tc: Add support for configuring the taprio scheduler

2018-07-13 Thread Vinicius Costa Gomes
This traffic scheduler allows traffic classes states (transmission allowed/not allowed, in the simplest case) to be scheduled, according to a pre-generated time sequence. This is the basis of the IEEE 802.1Qbv specification. If the controller supports it, traffic can be also marked as preemptable/