From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] big tcp
Date: Thu, 23 Feb 2023 07:41:18 +0200 [thread overview]
Message-ID: <E54B293B-A85E-428F-9016-C8E71E82CF13@gmail.com> (raw)
In-Reply-To: <CAA93jw6JQjJxaG9Wzpi4S9iW_=M6sD=6hnN6Z54XyJRS8+cyhA@mail.gmail.com>
> On 23 Feb, 2023, at 3:35 am, Dave Taht via Cake <cake@lists.bufferbloat.net> wrote:
>
> does this break cake?
>
> https://lore.kernel.org/netdev/de811bf3-e2d8-f727-72bc-c8a754a9d929@tessares.net/T/
It looks like they've included patches *to* Cake to handle anticipated breakage. This is one of the great things about having it upstreamed.
- Jonathan Morton
next prev parent reply other threads:[~2023-02-23 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 1:35 Dave Taht
2023-02-23 5:41 ` Jonathan Morton [this message]
2023-02-23 11:37 ` 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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E54B293B-A85E-428F-9016-C8E71E82CF13@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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