From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] fragmenting for lowest per flow latency
Date: Mon, 15 Jun 2015 18:40:13 -0700 [thread overview]
Message-ID: <CAA93jw7w=c9aTZKN6NL+krOXDkoaqMQ1x+XxdUwGEMk6eN-tWw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4kaShLxV6UzuN2e_3ZYN0f5xLZWarE_uRBV6gNn1Q5FA@mail.gmail.com>
On Mon, Jun 15, 2015 at 3:52 PM, Dave Taht <dave.taht@gmail.com> wrote:
> (I should probably create an alias for the crazy ideas like "devnull")
>
> but I have kind of wondered just how bad the fragmentation problem really was,
> and with peeling, already, we could also add fragmentation support, to
> create tons of fragments... and see what breaks, and get even lower
> per small packet flow latency when larger packets were present.
>
> I actually have a use case for this personally in that dnssec's rules
> (eDNS0) for fragmentation were a real pain in the arse of late, and
> *knowing* devices we work on handle fragments appropriately would be
> nice.
Whilst working through this crazy idea, I realized that the converse
might be useful,
doing reassembly of fragments along the way.
> --
> Dave Täht
> What will it take to vastly improve wifi for everyone?
> https://plus.google.com/u/0/explore/makewififast
--
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
prev parent reply other threads:[~2015-06-16 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 22:52 Dave Taht
2015-06-16 1:40 ` 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/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='CAA93jw7w=c9aTZKN6NL+krOXDkoaqMQ1x+XxdUwGEMk6eN-tWw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@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