From: Victor Nogueira <victor@mojatatu.com>
To: stephen@networkplumber.org, dsahern@kernel.org
Cc: jhs@mojatatu.com, deren.teo@outlook.com, andrew@lunn.ch,
netdev@vger.kernel.org
Subject: [PATCH iproute2 v2 0/3] Add JSON output support to the remaining qdiscs
Date: Tue, 3 Mar 2026 10:07:30 -0300 [thread overview]
Message-ID: <20260303130733.540278-1-victor@mojatatu.com> (raw)
Since qdisc core already assumes all qdiscs are able to output JSON,
add JSON output support to the remaning qdiscs (HFSC, QFQ, muiltiq)
so that a JSON qdisc dump outputs valid JSON.
v1 -> v2:
- Fix bug on line printing "level" field in HFSC (Pointed out by Stephen)
- Emit HFSC d (delay) as a raw numeric microseconds
value (Suggested by Stephen)
- Use nested JSON objects instead of flat names with spaces when
necessary in HFSC (Suggested by Stephen)
- Output bands and max_bands as separate JSON fields for
multiq (Suggested by Stephen)
Victor Nogueira (3):
tc: Add JSON output support to HFSC
tc: Add JSON output support to QFQ
tc: Add JSON output support to multiq
tc/q_hfsc.c | 27 +++++++++++++++++----------
tc/q_multiq.c | 6 +++++-
tc/q_qfq.c | 8 ++++----
3 files changed, 26 insertions(+), 15 deletions(-)
--
2.53.0
next reply other threads:[~2026-03-03 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 13:07 Victor Nogueira [this message]
2026-03-03 13:07 ` [PATCH iproute2 v2 1/3] tc: Add JSON output support to HFSC Victor Nogueira
2026-03-03 13:07 ` [PATCH iproute2 v2 2/3] tc: Add JSON output support to QFQ Victor Nogueira
2026-03-03 13:07 ` [PATCH iproute2 v2 3/3] tc: Add JSON output support to multiq Victor Nogueira
2026-03-07 1:20 ` [PATCH iproute2 v2 0/3] Add JSON output support to the remaining qdiscs patchwork-bot+netdevbpf
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=20260303130733.540278-1-victor@mojatatu.com \
--to=victor@mojatatu.com \
--cc=andrew@lunn.ch \
--cc=deren.teo@outlook.com \
--cc=dsahern@kernel.org \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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