From: Ferenc Fejes <primalgamer@gmail.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>, netdev@vger.kernel.org
Cc: "David Ahern" <dsahern@kernel.org>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Péter Antal" <antal.peti99@gmail.com>
Subject: Re: [PATCH iproute2-next 0/9] Add tc-mqprio and tc-taprio support for preemptible traffic classes
Date: Mon, 03 Apr 2023 13:18:07 +0200 [thread overview]
Message-ID: <6546e93dca588c3c01e56466e6f5ae10e37870bf.camel@gmail.com> (raw)
In-Reply-To: <20230403105245.2902376-1-vladimir.oltean@nxp.com>
Hi Vladimir!
On Mon, 2023-04-03 at 13:52 +0300, Vladimir Oltean wrote:
> This is the iproute2 support for the tc program to make use of the
> kernel feature for preemptible traffic classes described here:
> https://patchwork.kernel.org/project/netdevbpf/cover/20230403103440.2895683-1-vladimir.oltean@nxp.com/
>
> The state of the man pages prior to this work was a bit
> unsatisfactory,
> so patches 03-07 contain some man page cleanup in tc-taprio(8) and
> tc-mqprio(8).
>
> Vladimir Oltean (9):
> uapi: add definitions for preemptible traffic classes in mqprio and
> taprio
> utils: add max() definition
> tc/taprio: add max-sdu to the man page SYNOPSIS section
> tc/taprio: add a size table to the examples from the man page
Seems like Stephen merged Péter's manpages patch [1] but IMO your
version [2] is a better overhaul of that, also Péter ACK-ed to go
forward with that version. Looks like you rebased this work on the new
manpages, you have any plan to submit the changes from [2] separately?
Probably Stephen missed the whole discussion and about [2] and I'm
admit that putting acked/reviewed into a mail inside the discussion
might be misleading (probably thats show up for the original patch in
patchwork). Sorry for making it complicated.
> tc/mqprio: fix stray ] in man page synopsis
> tc/mqprio: use words in man page to express min_rate/max_rate
> dependency on bw_rlimit
> tc/mqprio: break up synopsis into multiple lines
> tc/mqprio: add support for preemptible traffic classes
> tc/taprio: add support for preemptible traffic classes
>
> include/uapi/linux/pkt_sched.h | 17 ++++++
> include/utils.h | 8 +++
> man/man8/tc-mqprio.8 | 92 ++++++++++++++++++++++---------
> man/man8/tc-taprio.8 | 27 ++++++++--
> tc/q_mqprio.c | 98
> +++++++++++++++++++++++++++++++++
> tc/q_taprio.c | 99 +++++++++++++++++++++++++-------
> --
> 6 files changed, 289 insertions(+), 52 deletions(-)
>
[1]
https://lore.kernel.org/netdev/167789641838.26474.2747633103367439718.git-patchwork-notify@kernel.org/
[2]
https://lore.kernel.org/netdev/20230220161809.t2vj6daixio7uzbw@skbuf/
Best,
Ferenc
next prev parent reply other threads:[~2023-04-03 11:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 10:52 [PATCH iproute2-next 0/9] Add tc-mqprio and tc-taprio support for preemptible traffic classes Vladimir Oltean
2023-04-03 10:52 ` [PATCH iproute2-next 1/9] uapi: add definitions for preemptible traffic classes in mqprio and taprio Vladimir Oltean
2023-04-03 10:52 ` [PATCH iproute2-next 2/9] utils: add max() definition Vladimir Oltean
2023-04-03 10:52 ` [PATCH iproute2-next 3/9] tc/taprio: add max-sdu to the man page SYNOPSIS section Vladimir Oltean
2023-04-03 10:52 ` [PATCH iproute2-next 4/9] tc/taprio: add a size table to the examples from the man page Vladimir Oltean
2023-04-03 10:52 ` [PATCH iproute2-next 5/9] tc/mqprio: fix stray ] in man page synopsis Vladimir Oltean
2023-04-03 10:52 ` [PATCH iproute2-next 6/9] tc/mqprio: use words in man page to express min_rate/max_rate dependency on bw_rlimit Vladimir Oltean
2023-04-03 10:52 ` [PATCH iproute2-next 7/9] tc/mqprio: break up synopsis into multiple lines Vladimir Oltean
2023-04-03 10:52 ` [PATCH iproute2-next 8/9] tc/mqprio: add support for preemptible traffic classes Vladimir Oltean
2023-04-03 10:52 ` [PATCH iproute2-next 9/9] tc/taprio: " Vladimir Oltean
2023-04-03 11:18 ` Ferenc Fejes [this message]
2023-04-03 11:23 ` [PATCH iproute2-next 0/9] Add tc-mqprio and tc-taprio " Vladimir Oltean
2023-04-03 11:30 ` Ferenc Fejes
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=6546e93dca588c3c01e56466e6f5ae10e37870bf.camel@gmail.com \
--to=primalgamer@gmail.com \
--cc=antal.peti99@gmail.com \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vladimir.oltean@nxp.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