Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Richard Smith" <smithbone@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Bloat] great interview on the scale conference wifi successes
Date: Thu, 12 Mar 2015 12:13:49 -0400 (EDT)	[thread overview]
Message-ID: <1426176829.336613096@apps.rackspace.com> (raw)
In-Reply-To: <5501B16E.9040207@gmail.com>

On Thursday, March 12, 2015 11:31am, "Richard Smith" <smithbone@gmail.com> said:

> On 03/10/2015 05:12 PM, Dave Taht wrote:
> 
>>>
>>> This year I deployed 53 APs. I'll make an updated map showing where they
>>> were deployed.
>>
>> So far as I know all the APs were fq-codeled, but the firewall/gw was
>> not.
> 
> How does this work?  I thought the AP's in this setup were run as bridges.

Pretty good question! Of course if AP's running as Ethernet bridges are bloated (meaning their queues can grow quite large) that's yet another reason that we need to make WiFi fast (by putting codel into the bridge function).

Ethernet bridges should definitely manage their outbound queues to keep the queues in them on the average quite small (average < 2 frames in steady state). Otherwise, if the outbound queue runs at 802.11b rates, and the inbound queues run at 802.11ac rates, there will be a serious disaster.

Since you can't ECN generalized Ethernet packets, codel would have to drop packets. And this might have been what David Lang is doing. (of course, it's perfectly reasonable if you know that the LAN is transporting an IP datagram, to ECN-mark those datagrams.  This is what an Internet transport layer is allowed to do, which is why ECN is part of the envelope, not the contents of the end-to-end packet.

The same argument applies to packets held for retransmission over an 802.11 link. It's perfectly OK to hold a packet outside the outbound queue for retransmission when the conditions to the destination get better, but that packet should not block the next packet coming in going to a different destination.  The retransmission queue (which is there to improve reliability) is a different thing.  [However, my intuition suggests that only one packet per next hop should be in the retransmission queue, and it should not stay there very long - after a period of time, let the sender at the next layer up figure out what to do. Propagation changes in the 10's of millisecond time frame. It won't get better if you wait 1/2 second or more]





  reply	other threads:[~2015-03-12 16:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 18:26 [Cerowrt-devel] " Dave Taht
2015-03-10 20:44 ` [Cerowrt-devel] [Bloat] " David Lang
2015-03-10 21:12   ` Dave Taht
2015-03-10 21:34     ` David Lang
2015-03-12 15:31     ` Richard Smith
2015-03-12 16:13       ` dpreed [this message]
2015-03-12 23:58         ` David Lang
2015-03-13  0:08           ` Dave Taht
2015-03-13  0:53             ` David Lang

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=1426176829.336613096@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=smithbone@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