lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 31 Oct 2022 13:20:15 +0000
To:     Vladimir Oltean <>
Subject: Re: [PATCH v3 iproute2-next] taprio: support dumping and setting per-tc
 max SDU


This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <>:

On Fri, 28 Oct 2022 14:50:53 +0300 you wrote:
> The 802.1Q queueMaxSDU table is technically implemented in Linux as
> nest. Multiple TCA_TAPRIO_ATTR_TC_ENTRY nests may appear in the netlink
> message, one per traffic class. Other configuration items that are per
> traffic class are also supposed to go there.
> This is done for future extensibility of the netlink interface (I have
> the feeling that the struct tc_mqprio_qopt passed through
> TCA_TAPRIO_ATTR_PRIOMAP is not exactly extensible, which kind of defeats
> the purpose of using netlink). But otherwise, the max-sdu is parsed from
> the user, and printed, just like any other fixed-size 16 element array.
> [...]

Here is the summary with links:
  - [v3,iproute2-next] taprio: support dumping and setting per-tc max SDU

You are awesome, thank you!
Deet-doot-dot, I am a bot.

Powered by blists - more mailing lists