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: Sat, 16 May 2020 13:37:39 -0700 (PDT) From: David Miller <davem@...emloft.net> To: vinicius.gomes@...el.com Cc: intel-wired-lan@...ts.osuosl.org, jeffrey.t.kirsher@...el.com, netdev@...r.kernel.org, vladimir.oltean@....com, po.liu@....com, m-karicheri2@...com, Jose.Abreu@...opsys.com Subject: Re: [next-queue RFC 0/4] ethtool: Add support for frame preemption From: Vinicius Costa Gomes <vinicius.gomes@...el.com> Date: Fri, 15 May 2020 18:29:44 -0700 > This series adds support for configuring frame preemption, as defined > by IEEE 802.1Q-2018 (previously IEEE 802.1Qbu) and IEEE 802.3br. > > Frame preemption allows a packet from a higher priority queue marked > as "express" to preempt a packet from lower priority queue marked as > "preemptible". The idea is that this can help reduce the latency for > higher priority traffic. Why do we need yet another name for something which is just basic traffic prioritization and why is this configured via ethtool instead of the "traffic classifier" which is where all of this stuff should be done?
Powered by blists - more mailing lists