Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Bob McMahon <bob.mcmahon@broadcom.com>
Cc: dpreed@deepplum.com, bloat-announce@lists.bufferbloat.net,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	cerowrt-devel@lists.bufferbloat.net,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] closing up my make-wifi-fast lab
Date: Mon, 27 Aug 2018 10:52:27 +0300	[thread overview]
Message-ID: <CB95C92E-E119-422C-BDEF-09C3CE2561D6@gmail.com> (raw)
In-Reply-To: <CAHb6LvpcSioG3dhyn4_EtWPxWTtkzYUgTS4wFkobnBZAJEoxrw@mail.gmail.com>

> On 27 Aug, 2018, at 10:06 am, Bob McMahon <bob.mcmahon@broadcom.com> wrote:
> 
> How can a centralized device predict the many "end stations'" network demand in its time scheduling?

DOCSIS does it by initially giving stations a tiny window into which to send requests for time, which are granted by the head-end.  This introduces some latency.  Further requests for time can be appended to a real transmission, which helps efficiency slightly.

Developing from that model, an AP might initially divide time evenly between stations, allowing them to send single large packets or several small packets without an explicit request for time - this is good for latency.  Along with that packet, the station could indicate to the AP that it has a queue of packets waiting, and the AP would take that into account when producing its next schedule.  It would also take into account its own queue.

It may be possible to combine TDM with orthogonal coding.  Here the AP monitors the received signal strength of its stations, and instructs them to change power so as to minimise the difference between them.  This maximises the SNR for each, should two transmit simultaneously.  The tradeoff, of course, is that orthogonal coding permits a reduction in waiting to transmit, but requires a reduction in data rate during the transmission.  I'm sure other people have better data on that than I do.

 - Jonathan Morton


  reply	other threads:[~2018-08-27  7:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-26 12:26 [Cerowrt-devel] " David P. Reed
2018-08-27  6:00 ` [Cerowrt-devel] [Make-wifi-fast] " Bob McMahon
2018-08-27  6:26   ` Jonathan Morton
2018-08-27  7:06     ` Bob McMahon
2018-08-27  7:52       ` Jonathan Morton [this message]
2018-08-27  8:34         ` Bob McMahon
2018-08-27 19:11           ` Bob McMahon
2018-08-27 19:45             ` Jonathan Morton
2018-08-27 19:59               ` Bob McMahon
     [not found]               ` <alpine.DEB.2.02.1808271431590.2583@nftneq.ynat.uz>
2018-08-28  1:47                 ` [Cerowrt-devel] [Bloat] " Bob McMahon
     [not found]                   ` <alpine.DEB.2.02.1808271750490.2583@nftneq.ynat.uz>
2018-08-28  1:56                     ` Bob McMahon
2018-08-30 19:12               ` [Cerowrt-devel] " bkil
2018-08-30 19:17                 ` Bob McMahon
2018-08-30 20:36                   ` bkil
2018-09-03 19:30                     ` Bob McMahon
2018-08-27  7:24     ` [Cerowrt-devel] [Bloat] " Luca Muscariello
2018-08-27  7:39       ` Bob McMahon
2018-08-27  7:52         ` Luca Muscariello
2018-08-30 19:12 ` [Cerowrt-devel] " bkil

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CB95C92E-E119-422C-BDEF-09C3CE2561D6@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat-announce@lists.bufferbloat.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=bob.mcmahon@broadcom.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@deepplum.com \
    --cc=make-wifi-fast@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