From: David Lang <david@lang.hm>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: stephen@networkplumber.org, cake@lists.bufferbloat.net,
bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Two questions re high speed congestion management anddatagram protocols
Date: Tue, 27 Jun 2023 12:47:01 -0700 (PDT) [thread overview]
Message-ID: <4np8q9q1-on99-rn94-5s1p-55643oo11037@ynat.uz> (raw)
In-Reply-To: <1687837319.447910185@mobile.rackspace.com>
On Mon, 26 Jun 2023, David P. Reed via Bloat wrote:
> Sorry for top posting, but ... Bigger question:
> Why would DCCP be deprecated by Linux kernel?
> Who makes that decision? Who argues against it?
Linus or the networking maintaners make the decision.
Usually things get pulled from the kernel because there are updates that need to
be made to the code (to match changes elsewhere in the kernel or because of
security issues) and there isn't a maintainer who works on the code in a
resonable time. This means that the maintainers for the general code area (in
this case networking maintainers) will need to do extra work in an area they
aren't that interested in (and, especially in the case of hardware, may not have
the ability to test). They do some of it, especially if it's commonly used, but
eventually either another maintainer steps up, or it goes away
David Lang
next prev parent reply other threads:[~2023-06-27 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 3:41 David P. Reed
2023-06-27 14:56 ` Stephen Hemminger
2023-06-28 9:43 ` Erik Auerswald
2023-06-27 19:47 ` David Lang [this message]
2023-06-27 22:49 ` Stephen Hemminger
2023-06-28 2:03 ` [Bloat] [Cake] " Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4np8q9q1-on99-rn94-5s1p-55643oo11037@ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=dpreed@deepplum.com \
--cc=stephen@networkplumber.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox