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]
Message-ID: <20230516164423.3e5b45e9@hermes.local>
Date: Tue, 16 May 2023 16:44:23 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Thorsten Glaser <t.glaser@...ent.de>
Cc: Toke Høiland-Jørgensen <toke@...e.dk>, Jakub
 Kicinski <kuba@...nel.org>, netdev@...r.kernel.org, Haye.Haehne@...ekom.de
Subject: Re: knob to disable locally-originating qdisc optimisation?

On Wed, 17 May 2023 01:40:23 +0200 (CEST)
Thorsten Glaser <t.glaser@...ent.de> wrote:

> On Tue, 16 May 2023, Stephen Hemminger wrote:
> 
> >If your qdisc was upstream, others could collaborate to resolve the issue.
> >As it stands, the kernel development process is intentionally hostile
> >to out of tree developer changes like this.  
> 
> The qdisc is a simulation for the network connection of one
> 5G UE. It’s not suitable as general router qdisc. I doubt
> it would even be considered for acceptance. The kernel
> upstreaming process is not the least hostile either…


Sounds like it could be extension or part of existing netem.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ