From: Jeremy Harris <jgh@wizmail.org>
To: ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] pacing, applied differently than bbr
Date: Sun, 9 Feb 2020 23:09:56 +0000 [thread overview]
Message-ID: <a3b441d7-2f5b-7d7e-7210-d4faebbd0e1b@wizmail.org> (raw)
In-Reply-To: <CAA93jw6FQb7ES-ZuFWfsM=FncCG7cwjZ5O-18uaCYystt8YSEg@mail.gmail.com>
On 09/02/2020 07:11, Dave Taht wrote:
> I don't know how I stumbled across this, but it seemed interesting at
> this late hour. I wonder if they kept at it or tried ecn also.
>
> "A Model Predictive Control Approach to Flow Pacing for TCP"
Y'know, it'd be really useful if NICs handled pacing as well
as segment-offload.
--
Cheers,
Jeremy
prev parent reply other threads:[~2020-02-09 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 7:11 Dave Taht
2020-02-09 18:21 ` David Fridovich-Keil
2020-02-09 23:09 ` Jeremy Harris [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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3b441d7-2f5b-7d7e-7210-d4faebbd0e1b@wizmail.org \
--to=jgh@wizmail.org \
--cc=ecn-sane@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