From: Paolo Abeni <pabeni@redhat.com>
To: chia-yu.chang@nokia-bell-labs.com, xandfury@gmail.com,
netdev@vger.kernel.org, dave.taht@gmail.com, jhs@mojatatu.com,
kuba@kernel.org, stephen@networkplumber.org,
xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, horms@kernel.org, andrew+netdev@lunn.ch,
donald.hunter@gmail.com, ast@fiberby.net, liuhangbin@gmail.com,
shuah@kernel.org, linux-kselftest@vger.kernel.org, ij@kernel.org,
ncardwell@google.com, koen.de_schepper@nokia-bell-labs.com,
g.white@cablelabs.com, ingemar.s.johansson@ericsson.com,
mirja.kuehlewind@ericsson.com, cheshire@apple.com,
rs.ietf@gmx.at, Jason_Livingood@comcast.com,
vidhi_goel@apple.com
Subject: Re: [PATCH v11 net-next 1/5] Documentation: netlink: specs: tc: Add DualPI2 specification
Date: Tue, 22 Apr 2025 11:53:34 +0200 [thread overview]
Message-ID: <949655cd-4690-4513-a24e-7f1e035425b0@redhat.com> (raw)
In-Reply-To: <20250415124317.11561-2-chia-yu.chang@nokia-bell-labs.com>
On 4/15/25 2:43 PM, chia-yu.chang@nokia-bell-labs.com wrote:
> From: Chia-Yu Chang <chia-yu.chang@nokia-bell-labs.com>
>
> Introduce the specification of tc qdisc DualPI2 stats and attributes,
> which is the reference implementation of IETF RFC9332 DualQ Coupled AQM
> (https://datatracker.ietf.org/doc/html/rfc9332) providing two different
> queues: low latency queue (L-queue) and classic queue (C-queue).
>
> Signed-off-by: Chia-Yu Chang <chia-yu.chang@nokia-bell-labs.com>
> ---
> Documentation/netlink/specs/tc.yaml | 144 ++++++++++++++++++++++++++++
> 1 file changed, 144 insertions(+)
>
> diff --git a/Documentation/netlink/specs/tc.yaml b/Documentation/netlink/specs/tc.yaml
> index aacccea5dfe4..0fb971935285 100644
> --- a/Documentation/netlink/specs/tc.yaml
> +++ b/Documentation/netlink/specs/tc.yaml
> @@ -816,6 +816,58 @@ definitions:
> -
> name: drop-overmemory
> type: u32
> + -
> + name: tc-dualpi2-xstats
> + type: struct
> + members:
> + -
> + name: prob
> + type: u32
> + doc: Current probability
> + -
> + name: delay_c
> + type: u32
> + doc: Current C-queue delay in microseconds
> + -
> + name: delay_l
> + type: u32
> + doc: Current L-queue delay in microseconds
> + -
> + name: pkts_in_c
> + type: u32
> + doc: Number of packets enqueued in the C-queue
> + -
> + name: pkts_in_l
> + type: u32
> + doc: Number of packets enqueued in the L-queue
> + -
> + name: maxq
> + type: u32
> + doc: Maximum number of packets seen by the DualPI2
> + -
> + name: ecn_mark
> + type: u32
> + doc: All packets marked with ecn
> + -
> + name: step_mark
> + type: u32
> + doc: Only packets marked with ecn due to L-queue step AQM
> + -
> + name: credit
> + type: s32
> + doc: Current credit value for WRR
> + -
> + name: memory_used
> + type: u32
> + doc: Memory used in bytes by the DualPI2
> + -
> + name: max_memory_used
> + type: u32
Here and in other numeric fields you should probably want to use 'uint'
type, that will allow either 32 or 64 bits integers depending on the
actual value and will make possible overflows harder.
> + doc: Maximum memory used in bytes by the DualPI2
> + -
> + name: memory_limit
> + type: u32
> + doc: Memory limit in bytes
> -
> name: tc-fq-pie-xstats
> type: struct
> @@ -2299,6 +2351,92 @@ attribute-sets:
> -
> name: quantum
> type: u32
> + -
> + name: tc-dualpi2-attrs
> + attributes:
> + -
> + name: limit
> + type: u32
> + doc: Limit of total number of packets in queue
> + -
> + name: memlimit
> + type: u32
> + doc: Memory limit of total number of packets in queue
> + -
> + name: target
> + type: u32
> + doc: Classic target delay in microseconds
> + -
> + name: tupdate
> + type: u32
> + doc: Drop probability update interval time in microseconds
> + -
> + name: alpha
> + type: u32
> + doc: Integral gain factor in Hz for PI controller
> + -
> + name: beta
> + type: u32
> + doc: Proportional gain factor in Hz for PI controller
> + -
> + name: step_thresh
> + type: u32
> + doc: L4S step marking threshold in microseconds or in packet (see step_packets)
> + -
> + name: step_packets
> + type: flags
> + doc: L4S Step marking threshold unit
> + entries:
> + - microseconds
> + - packets
> + -
> + name: min_qlen_step
> + type: u32
> + doc: Pacekts enqueued to the L-queue can apply the step threshold when the queue length of L-queue is larger than this value. (0 is recommended)
Typo above, should likely be 'Packets'
/P
next prev parent reply other threads:[~2025-04-22 9:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 12:43 [PATCH v11 net-next 0/5] DUALPI2 patch chia-yu.chang
2025-04-15 12:43 ` [PATCH v11 net-next 1/5] Documentation: netlink: specs: tc: Add DualPI2 specification chia-yu.chang
2025-04-22 9:53 ` Paolo Abeni [this message]
2025-04-22 15:30 ` Chia-Yu Chang (Nokia)
2025-04-15 12:43 ` [PATCH v11 net-next 2/5] selftests/tc-testing: Add selftests for qdisc DualPI2 chia-yu.chang
2025-04-16 13:52 ` Jakub Kicinski
2025-04-16 14:00 ` Victor Nogueira
2025-04-16 22:19 ` Jakub Kicinski
2025-04-17 0:18 ` Victor Nogueira
2025-04-15 12:43 ` [PATCH v11 net-next 3/5] sched: Struct definition and parsing of dualpi2 qdisc chia-yu.chang
2025-04-22 10:07 ` Paolo Abeni
2025-04-22 15:28 ` Chia-Yu Chang (Nokia)
2025-04-15 12:43 ` [PATCH v11 net-next 4/5] sched: Dump configuration and statistics " chia-yu.chang
2025-04-15 12:43 ` [PATCH v11 net-next 5/5] sched: Add enqueue/dequeue " chia-yu.chang
2025-04-22 10:21 ` Paolo Abeni
2025-04-15 14:58 ` [PATCH v11 net-next 0/5] DUALPI2 patch Jakub Kicinski
2025-04-15 15:05 ` Chia-Yu Chang (Nokia)
2025-04-15 15:35 ` 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=949655cd-4690-4513-a24e-7f1e035425b0@redhat.com \
--to=pabeni@redhat.com \
--cc=Jason_Livingood@comcast.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@fiberby.net \
--cc=cheshire@apple.com \
--cc=chia-yu.chang@nokia-bell-labs.com \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=g.white@cablelabs.com \
--cc=horms@kernel.org \
--cc=ij@kernel.org \
--cc=ingemar.s.johansson@ericsson.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=koen.de_schepper@nokia-bell-labs.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=mirja.kuehlewind@ericsson.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=rs.ietf@gmx.at \
--cc=shuah@kernel.org \
--cc=stephen@networkplumber.org \
--cc=vidhi_goel@apple.com \
--cc=xandfury@gmail.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