From: Dave Taht <dave.taht@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: David Lang <david@lang.hm>,
cake@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Cake] Two questions re high speed congestion management anddatagram protocols
Date: Tue, 27 Jun 2023 20:03:39 -0600 [thread overview]
Message-ID: <CAA93jw4uBMw7xkAkiB8L16tPNpdj+tg430p5pUb96rMK06hMKA@mail.gmail.com> (raw)
In-Reply-To: <20230627154931.71aff7ca@hermes.local>
https://datatracker.ietf.org/doc/charter-ietf-ccwg/
is a new wg intended to poke into these issues
On Tue, Jun 27, 2023 at 4:49 PM Stephen Hemminger via Cake
<cake@lists.bufferbloat.net> wrote:
>
> On Tue, 27 Jun 2023 12:47:01 -0700 (PDT)
> David Lang <david@lang.hm> wrote:
>
> > 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
>
> See https://patchwork.kernel.org/project/netdevbpf/patch/20230614194705.90673-3-kuniyu@amazon.com/
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
--
Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
Dave Täht CSO, LibreQos
prev parent reply other threads:[~2023-06-28 2:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 3:41 [Bloat] " David P. Reed
2023-06-27 14:56 ` Stephen Hemminger
2023-06-28 9:43 ` Erik Auerswald
2023-06-27 19:47 ` David Lang
2023-06-27 22:49 ` Stephen Hemminger
2023-06-28 2:03 ` Dave Taht [this message]
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=CAA93jw4uBMw7xkAkiB8L16tPNpdj+tg430p5pUb96rMK06hMKA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=david@lang.hm \
--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