lists.openwall.net | 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
| ||
|
Date: Mon, 31 Oct 2022 13:20:15 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Vladimir Oltean <vladimir.oltean@....com> Cc: netdev@...r.kernel.org, dsahern@...nel.org, stephen@...workplumber.org, vinicius.gomes@...el.com, jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us Subject: Re: [PATCH v3 iproute2-next] taprio: support dumping and setting per-tc max SDU Hello: This patch was applied to iproute2/iproute2-next.git (main) by David Ahern <dsahern@...nel.org>: On Fri, 28 Oct 2022 14:50:53 +0300 you wrote: > The 802.1Q queueMaxSDU table is technically implemented in Linux as > the TCA_TAPRIO_TC_ENTRY_MAX_SDU attribute of the TCA_TAPRIO_ATTR_TC_ENTRY > 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 https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=b10a6509c195 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists