From: Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>
To: netdev@vger.kernel.org
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>
Subject: [RFC v3 iproute2 2/3] uapi pkt_sched: Add tbs info - DO NOT COMMIT
Date: Tue, 6 Mar 2018 17:16:07 -0800 [thread overview]
Message-ID: <20180307011608.24186-2-jesus.sanchez-palencia@intel.com> (raw)
In-Reply-To: <20180307011608.24186-1-jesus.sanchez-palencia@intel.com>
This should come from the next uapi headers update.
Sending it now just as a convenience so anyone can build tc with tbs
support.
Signed-off-by: Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>
---
include/uapi/linux/pkt_sched.h | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/include/uapi/linux/pkt_sched.h b/include/uapi/linux/pkt_sched.h
index 37b5096a..92af9fa4 100644
--- a/include/uapi/linux/pkt_sched.h
+++ b/include/uapi/linux/pkt_sched.h
@@ -934,4 +934,22 @@ enum {
#define TCA_CBS_MAX (__TCA_CBS_MAX - 1)
+
+/* TBS */
+struct tc_tbs_qopt {
+ __s32 delta;
+ __s32 clockid;
+ __u32 flags;
+#define TC_TBS_SORTING_ON BIT(0)
+#define TC_TBS_OFFLOAD_ON BIT(1)
+};
+
+enum {
+ TCA_TBS_UNSPEC,
+ TCA_TBS_PARMS,
+ __TCA_TBS_MAX,
+};
+
+#define TCA_TBS_MAX (__TCA_TBS_MAX - 1)
+
#endif
--
2.16.2
next prev parent reply other threads:[~2018-03-07 1:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 1:16 [RFC v3 iproute2 1/3] include: Add ptp_clock.h to linux uapi Jesus Sanchez-Palencia
2018-03-07 1:16 ` Jesus Sanchez-Palencia [this message]
2018-03-07 1:16 ` [RFC v3 iproute2 3/3] tc: Add support for the TBS Qdisc Jesus Sanchez-Palencia
2018-03-07 1:51 ` Stephen Hemminger
2018-03-07 22:29 ` Jesus Sanchez-Palencia
2018-03-07 22:53 ` Stephen Hemminger
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=20180307011608.24186-2-jesus.sanchez-palencia@intel.com \
--to=jesus.sanchez-palencia@intel.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--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