General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Sebastian Moeller" <moeller0@gmx.de>, "Dave Täht" <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] lwn.net's tcp small queues vs wifi aggregation solved
Date: Thu, 21 Jun 2018 21:51:55 +0200	[thread overview]
Message-ID: <87zhznq5no.fsf@toke.dk> (raw)
In-Reply-To: <6DCE29AF-5F91-4F06-93A8-0F5D197C9D06@gmx.de>

Sebastian Moeller <moeller0@gmx.de> writes:

> 	To make up for the fact that wireless uses unfortunately uses a
> 	very high per packet overhead it just tries to "hide" by
> 	amortizing it over more than one data packet. How about trying
> 	to find a better, less wasteful MAC instead ;) (and now we have
> 	two problems...) Now really from a latency perspective it
> 	clearly is better to ovoid overhead instead of use "batching" to
> 	better amortize it since batching increases latency (I stipulate
> 	that there are condition in which clever batching will not
> 	increase the noticeable latency if it can hide inside another
> 	latency increasing process).

Seems that 802.11ax will have some interesting features to this end.
Specifically, the spectrum can be split, allowing smaller chunks of it
to be used for reverse path transmissions (full-duplex at last?).

https://en.wikipedia.org/wiki/802.11ax#Technical_improvements

Also, 1024-QAM on 160Mhz channels; omg...

-Toke

  reply	other threads:[~2018-06-21 19:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21  4:58 Dave Taht
2018-06-21  9:22 ` Toke Høiland-Jørgensen
2018-06-21 12:55   ` Eric Dumazet
2018-06-21 15:18     ` Dave Taht
2018-06-21 15:31       ` Caleb Cushing
2018-06-21 15:46         ` Stephen Hemminger
2018-06-21 17:41           ` Caleb Cushing
2018-06-21 15:50         ` Dave Taht
2018-06-21 16:29       ` David Collier-Brown
2018-06-21 16:54         ` Jonathan Morton
2018-06-21 16:43       ` Kathleen Nichols
2018-06-21 19:17         ` Dave Taht
2018-06-21 19:41           ` Sebastian Moeller
2018-06-21 19:51             ` Toke Høiland-Jørgensen [this message]
2018-06-21 19:54             ` Dave Taht
2018-06-21 20:11               ` Sebastian Moeller
2018-06-22 14:01           ` Kathleen Nichols
2018-06-22 14:12             ` Jonathan Morton
2018-06-22 14:49               ` Michael Richardson
2018-06-22 15:02                 ` Jonathan Morton
2018-06-22 21:55                   ` Michael Richardson
2018-06-25 10:38                     ` Toke Høiland-Jørgensen
2018-06-25 23:54                       ` Jim Gettys
2018-06-26  0:07                         ` Jonathan Morton
2018-06-26  0:21                           ` David Lang
2018-06-26  0:36                             ` Simon Barber
2018-06-26  0:44                               ` Jonathan Morton
2018-06-26  0:52                                 ` Jim Gettys
2018-06-26  0:56                                 ` David Lang
2018-06-26 11:16                                   ` Toke Høiland-Jørgensen
2018-06-26  1:27                                 ` Dave Taht
2018-06-26  3:30                                   ` Simon Barber

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=87zhznq5no.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=moeller0@gmx.de \
    /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