Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Simon Barber <simon@superduper.net>
To: Rich Brown <richb.hanover@gmail.com>,
	Jonathan Morton <chromatix99@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] [tsvwg] Comments on draft-szigeti-tsvwg-ieee-802-11e
Date: Sat, 08 Aug 2015 07:25:04 -0700	[thread overview]
Message-ID: <14f0db33ed8.27f7.e972a4f4d859b00521b2b659602cb2f9@superduper.net> (raw)
In-Reply-To: <4DB19372-E89D-4153-B8DC-999555FE0363@gmail.com>

Some level of hardware queueing is necessary to meet the response time. 
It's further complicated by the need to include retries at the start of the 
next aggregate, but you only learn which ones from the block-ACK received 
after the last one. Given the hardware's need to have frame length well 
before the data you may have only a few microseconds to make some 
decisions. This is why all recent chipsets have a fairly fast CPU on board 
dedicated to implementing some of these functions. Of course the quality of 
the design and implementation varies hugely from vendor to vendor, and the 
API in terms of queueing varies.

Simon

Sent with AquaMail for Android
http://www.aqua-mail.com


On August 7, 2015 10:36:04 AM Rich Brown <richb.hanover@gmail.com> wrote:

> Ah..., the bitter bit of the reality sandwich. Yum :-(
>
> But Dave's note about Felix's hook for per-station queueing makes it seem 
> feasible, if only a lot of work.
>
> Thanks, all, for the enlightenment!
>
> Rich
>
> On Aug 7, 2015, at 9:28 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
> >
> >> On 7 Aug, 2015, at 15:22, Rich Brown <richb.hanover@gmail.com> wrote:
> >>
> >> - At that time, the wifi driver requests packets from fq_codel until a) 
> the the fq_codel queues are empty, or b) the wifi frame is full. In either 
> case, the wifi driver sends what it has.
> >
> > There’s one big flaw with this: if packets are available for multiple 
> destinations, fq_codel will generally give you a variety pack of packets 
> for each of them.  But a wifi TXOP is for a single destination, so only 
> some of the packets would be eligible for the same aggregate frame.
> >
> > So what’s needed is a way for the wifi driver to tell the queue that it 
> wants packets for the *same* destination as it’s transmitting to.
> >
> >> - Once the transmit opportunity has come around, it's a matter of 
> microseconds (I assume) to pull in a wifi frame's worth of packets from 
> fq_codel
> >
> > This is hard to guarantee in software in a general-purpose OS.
> >
> > - Jonathan Morton
> >
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast



  reply	other threads:[~2015-08-08 14:25 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E9C29602-7F1D-43AD-980C-050B58FA0AC6@iii.ca>
2015-07-23  6:48 ` [Cerowrt-devel] Fwd: " Dave Taht
2015-07-23  7:44   ` Jonathan Morton
2015-07-23  7:49     ` Alan Jenkins
2015-07-24 10:38       ` [Cerowrt-devel] [Make-wifi-fast] " Sebastian Moeller
2015-07-30 20:29   ` [Cerowrt-devel] " Jonathan Morton
2015-07-30 21:35     ` [Cerowrt-devel] [Make-wifi-fast] " Sebastian Moeller
2015-07-30 21:56       ` Jonathan Morton
2015-07-31  3:27         ` Sebastian Moeller
2015-07-31 16:47           ` dpreed
2015-07-31 17:04             ` Jonathan Morton
2015-07-31 20:23               ` Michael Richardson
2015-07-31 20:45                 ` Jonathan Morton
2015-08-03 15:44               ` dpreed
2015-08-03 16:14                 ` David Lang
2015-08-03 23:37                   ` dpreed
2015-08-03 23:52                     ` Jonathan Morton
2015-08-04  0:13                     ` David Lang
2015-08-04 16:55                       ` dpreed
2015-08-07  8:28             ` Mikael Abrahamsson
2015-08-07 13:22               ` Rich Brown
2015-08-07 13:28                 ` Jonathan Morton
2015-08-07 17:35                   ` Rich Brown
2015-08-08 14:25                     ` Simon Barber [this message]
2015-08-07 20:03                   ` David Lang
2015-08-07 21:46                     ` dpreed
2015-08-07 22:31                       ` David Lang
2015-08-08 20:46                         ` dpreed
2015-08-08 23:23                           ` David Lang
2015-08-09 19:31                             ` Jonathan Morton
2015-08-09 21:50                               ` David Lang
2015-08-10  5:39                                 ` Mikael Abrahamsson
2015-08-13 21:48                               ` David Lang
2015-08-13 22:14                                 ` Jonathan Morton
2015-08-13 22:25                                   ` David Lang
2015-08-13 22:30                                     ` Jonathan Morton
2015-08-09 22:09                           ` David Lang
2015-08-10 13:48                         ` 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/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=14f0db33ed8.27f7.e972a4f4d859b00521b2b659602cb2f9@superduper.net \
    --to=simon@superduper.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=richb.hanover@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