From: Jiri Pirko <jiri@resnulli.us>
To: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Cc: netdev@vger.kernel.org, jesus.sanchez-palencia@intel.com,
tglx@linutronix.de, jan.altenberg@linutronix.de,
henrik@austad.us, richardcochran@gmail.com,
levi.pearson@harman.com, jhs@mojatatu.com,
xiyou.wangcong@gmail.com
Subject: Re: [RFC net-next v1 1/1] net/sched: Introduce the taprio scheduler
Date: Sat, 14 Jul 2018 08:45:05 +0200 [thread overview]
Message-ID: <20180714064505.GA2821@nanopsycho.orion> (raw)
In-Reply-To: <20180714000536.1008-2-vinicius.gomes@intel.com>
Sat, Jul 14, 2018 at 02:05:36AM CEST, vinicius.gomes@intel.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?
next prev parent reply other threads:[~2018-07-14 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 0:05 [RFC net-next v1 0/1] net/sched: Introduce the taprio scheduler Vinicius Costa Gomes
2018-07-14 0:05 ` [RFC net-next v1 1/1] " Vinicius Costa Gomes
2018-07-14 6:45 ` Jiri Pirko [this message]
2018-07-16 17:13 ` Vinicius Costa Gomes
2018-07-16 21:06 ` Jakub Kicinski
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=20180714064505.GA2821@nanopsycho.orion \
--to=jiri@resnulli.us \
--cc=henrik@austad.us \
--cc=jan.altenberg@linutronix.de \
--cc=jesus.sanchez-palencia@intel.com \
--cc=jhs@mojatatu.com \
--cc=levi.pearson@harman.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
--cc=vinicius.gomes@intel.com \
--cc=xiyou.wangcong@gmail.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).