netdev - Re: Bypass qdiscs?

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Sun, 5 Nov 2023 21:27:35 -0700
From: David Ahern <dsahern@...nel.org>
To: Stephen Hemminger <stephen@...workplumber.org>,
 John Ousterhout <ouster@...stanford.edu>
Cc: Andrew Lunn <andrew@...n.ch>, netdev@...r.kernel.org
Subject: Re: Bypass qdiscs?

On 11/5/23 8:23 PM, Stephen Hemminger wrote:
> On Sat, 4 Nov 2023 19:47:30 -0700
> John Ousterhout <ouster@...stanford.edu> wrote:
> 
>> I haven't tried creating a "pass through" qdisc, but that seems like a
>> reasonable approach if (as it seems) there isn't something already
>> built-in that provides equivalent functionality.
>>
>> -John-
>>
>> P.S. If hardware starts supporting Homa, I hope that it will be
>> possible to move the entire transport to the NIC, so that applications
>> can bypass the kernel entirely, as with RDMA.
> 
> One old trick was setting netdev queue length to 0 to avoid qdisc.
> 

tc qdisc replace dev <name> root noqueue

should work