From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: netdev@vger.kernel.org
Cc: Vinicius Costa Gomes <vinicius.gomes@intel.com>,
jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
jesus.sanchez-palencia@intel.com, ilias.apalodimas@linaro.org,
simon.fok@baesystems.com
Subject: [PATCH iproute2 net-next v1 0/6] introduce the taprio scheduler
Date: Fri, 28 Sep 2018 18:10:44 -0700 [thread overview]
Message-ID: <20180929011050.14056-1-vinicius.gomes@intel.com> (raw)
Hi,
Changes from RFC:
- Removed support for the sched-file parameter, in favor of
supporting the batch mode feature;
This is the iproute2 side of the taprio v1 series.
Please see the kernel side cover letter for more information about how
to test this.
Cheers,
next reply other threads:[~2018-09-29 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 1:10 Vinicius Costa Gomes [this message]
2018-09-29 1:10 ` [PATCH iproute2 net-next v1 1/6] utils: Implement get_s64() Vinicius Costa Gomes
2018-09-29 1:10 ` [PATCH iproute2 net-next v1 2/6] include: Add helper to retrieve a __s64 from a netlink msg Vinicius Costa Gomes
2018-09-29 1:10 ` [PATCH iproute2 net-next v1 3/6] libnetlink: Add helper for getting a __s32 from netlink msgs Vinicius Costa Gomes
2018-09-29 1:10 ` [PATCH iproute2 net-next v1 4/6] include: add definitions for taprio [DO NOT COMMIT] Vinicius Costa Gomes
2018-09-29 1:10 ` [PATCH iproute2 net-next v1 5/6] tc: Add support for configuring the taprio scheduler Vinicius Costa Gomes
2018-10-03 16:36 ` David Ahern
2018-10-03 17:13 ` Vinicius Costa Gomes
2018-09-29 1:10 ` [PATCH iproute2 net-next v1 6/6] taprio: Add manpage for tc-taprio(8) 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=20180929011050.14056-1-vinicius.gomes@intel.com \
--to=vinicius.gomes@intel.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jesus.sanchez-palencia@intel.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=simon.fok@baesystems.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).