From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Rpm] receive window bug fix
Date: Sat, 3 Jun 2023 11:20:43 -0700 [thread overview]
Message-ID: <CALQXh-Ork51MPvbxJ53+RPUNWMV0_x-y2K7tCXgbXJ1Z6UYi3w@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7fUq4+4=UQjpuTr5tEs5h70LxD8nK5frUwDEr59cxGFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
This is good work! I love reading their posts on scale like this.
It’s wild to me that the Linux kernel has (apparently) never implemented
shrinking the receive window, or handling the case of userspace starting a
large transfer and then just not ever reading it… the latter is less
surprising, I guess, because that’s an application bug that you probably
would catch separately, and would be focused on fixing in the application
layer…
-Aaron
On Sat, Jun 3, 2023 at 1:04 AM Dave Taht via Rpm <rpm@lists.bufferbloat.net>
wrote:
> these folk do good work, and I loved the graphs
>
>
> https://blog.cloudflare.com/unbounded-memory-usage-by-tcp-for-receive-buffers-and-how-we-fixed-it/
>
> --
> Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
> Dave Täht CSO, LibreQos
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm
>
--
- Sent from my iPhone.
[-- Attachment #2: Type: text/html, Size: 1935 bytes --]
next prev parent reply other threads:[~2023-06-03 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 8:03 Dave Taht
2023-06-03 18:20 ` Aaron Wood [this message]
2023-06-03 19:15 ` rjmcmahon
2023-06-03 18:56 ` rjmcmahon
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALQXh-Ork51MPvbxJ53+RPUNWMV0_x-y2K7tCXgbXJ1Z6UYi3w@mail.gmail.com \
--to=woody77@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=rpm@lists.bufferbloat.net \
/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