[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180714064505.GA2821@nanopsycho.orion>
Date: Sat, 14 Jul 2018 08:45:05 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Vinicius Costa Gomes <vinicius.gomes@...el.com>
Cc: netdev@...r.kernel.org, jesus.sanchez-palencia@...el.com,
tglx@...utronix.de, jan.altenberg@...utronix.de, henrik@...tad.us,
richardcochran@...il.com, levi.pearson@...man.com,
jhs@...atatu.com, xiyou.wangcong@...il.com
Subject: Re: [RFC net-next v1 1/1] net/sched: Introduce the taprio scheduler
Sat, Jul 14, 2018 at 02:05:36AM CEST, vinicius.gomes@...el.com wrote:
>This scheduler allows the network administrator to configure schedules
>for classes of traffic, the configuration interface is similar to what
>IEEE 802.1Qbv-2015 defines.
>
>Example configuration:
>
>$ tc qdisc add dev enp2s0 parent root handle 100 taprio \
> num_tc 3 \
> map 2 2 1 0 2 2 2 2 2 2 2 2 2 2 2 2 \
> queues 1@0 1@1 2@2 \
> sched-file ~/gates.sched \
> base-time 1000000 \
> clockid CLOCK_TAI
>
>This qdisc borrows a few concepts from mqprio and most the parameters
>are similar to mqprio. The main difference is the 'sched-file'
>parameter, one example of a schedule file would be:
>
>gates.sched
Any particular reason this has to be in file and not on the cmdline?
Powered by blists - more mailing lists