From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: biz.tinalee@gmail.com, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] less than best effort: TCP - flexis - A New Approach To Incipient Congestion Detection and Control
Date: Sat, 2 Apr 2022 18:05:55 -0700 (PDT) [thread overview]
Message-ID: <nr68soro-7122-8p20-60np-8p2180r2oos1@ynat.uz> (raw)
In-Reply-To: <CAA93jw723BjTPSD7QqzEuA5XX=Cdh37v0shQzwtQa7RxOOK93g@mail.gmail.com>
On Sat, 2 Apr 2022, Dave Taht wrote:
> I have always disagreed with the "don't reduce segment size" crowd,
> btw. If you have a rate where you need to go below 2mss, it doesn't
> hurt the network to reduce the size of the packet, and you can keep
> the signal strength up by reducing that size and continuing to sample
> rtt, to respond quickly.
>
> Even if you are only passing a single byte of data, by lowering this
> below everyone else's 2mss noise floor, you still eventually win, and
> also you occupy space in packet fifos, reducing overall latency, as
> bytes=time. IMHO.
this ignores per-packet overhead (which is headers + inter-packet time). As data
rates get faster, the inter-packet time is not shrinking to match.
This is especially true in wifi where the headers are transmitted at a much
slower speed than the data for compatibility reasons (as there may be many
different data rates on any channel), but it still applies to wired networks.
David Lang
next prev parent reply other threads:[~2022-04-03 1:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 22:37 Dave Taht
2022-04-03 1:05 ` David Lang [this message]
2022-04-05 15:44 ` Qian Li
2022-04-07 0:52 ` Dave Taht
2022-04-07 14:35 ` Qian Li
2022-04-09 6:56 ` Qian Li
2022-08-21 18:27 ` Dave Taht
2022-08-22 4:27 ` Qian Li
2022-08-23 13:34 Qian Li
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=nr68soro-7122-8p20-60np-8p2180r2oos1@ynat.uz \
--to=david@lang.hm \
--cc=biz.tinalee@gmail.com \
--cc=bloat@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