From: Stephen Hemminger <stephen@networkplumber.org>
To: Thorsten Glaser <t.glaser@tarent.de>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Jakub Kicinski" <kuba@kernel.org>,
netdev@vger.kernel.org, Haye.Haehne@telekom.de
Subject: Re: knob to disable locally-originating qdisc optimisation?
Date: Tue, 16 May 2023 16:44:23 -0700 [thread overview]
Message-ID: <20230516164423.3e5b45e9@hermes.local> (raw)
In-Reply-To: <d3fcafc-08-a74e-8bc8-b93cfcd2f5ef@tarent.de>
On Wed, 17 May 2023 01:40:23 +0200 (CEST)
Thorsten Glaser <t.glaser@tarent.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.
next prev parent reply other threads:[~2023-05-16 23:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 12:54 knob to disable locally-originating qdisc optimisation? Thorsten Glaser
2023-04-27 20:21 ` Jakub Kicinski
2023-04-27 23:37 ` Stephen Hemminger
2023-05-16 16:38 ` Thorsten Glaser
2023-05-16 19:23 ` Toke Høiland-Jørgensen
2023-05-16 20:20 ` Thorsten Glaser
2023-05-16 22:11 ` Toke Høiland-Jørgensen
2023-05-16 23:01 ` Stephen Hemminger
2023-05-16 23:40 ` Thorsten Glaser
2023-05-16 23:44 ` Stephen Hemminger [this message]
2023-05-16 23:47 ` Thorsten Glaser
2023-05-17 3:02 ` Stephen Hemminger
2023-05-17 15:53 ` Thorsten Glaser
2023-05-16 23:41 ` Thorsten Glaser
2023-05-17 10:00 ` Toke Høiland-Jørgensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230516164423.3e5b45e9@hermes.local \
--to=stephen@networkplumber.org \
--cc=Haye.Haehne@telekom.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=t.glaser@tarent.de \
--cc=toke@toke.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.