From: Phineas Gage <phineas919@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: codel@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Codel] [Make-wifi-fast] Software rate limiting with fq_codel for point-to-point WiFi backhaul links
Date: Fri, 9 Dec 2016 13:37:55 +0100 [thread overview]
Message-ID: <5EA3C6E6-76C7-4347-9B14-3C310271A8FD@gmail.com> (raw)
In-Reply-To: <EB6A0AC3-908A-4E80-8283-E31CFC1C1483@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
Ok, I had not realized that, thanks. :)
I’ve not seen this done anywhere, has anyone tried it? Otherwise I’ll give it a try and write back what I find.
In this case, the throughput for the backhaul links “should” be mostly stable, and we’ll just accept any variation as “no worse than before”.
It's true, I also want to try Cake (anywhere I wrote fq_codel that could be substituted with Cake), and I see from here (https://www.bufferbloat.net/projects/codel/wiki/Cake/#installing-cake-out-of-tree-on-linux <https://www.bufferbloat.net/projects/codel/wiki/Cake/#installing-cake-out-of-tree-on-linux>) that it should work on the 3.16.7 kernel I need to target. Voyage Linux doesn’t install with kernel sources, but I should be able to get that compiled with their SDK.
> On Dec 9, 2016, at 12:39 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 9 Dec, 2016, at 12:12, Phineas Gage <phineas919@gmail.com> wrote:
>>
>> Given the half-duplex nature of 802.11 WiFi, is it possible to use fq_codel with software rate limiting on separate hardware from the WiFi radio, while still allowing at or near the full WiFi link rate?
>
> Given that you can’t reliably predict the actual wifi throughput from userspace, and that it will vary over time due to external interference and path attenuation, that would be difficult.
>
> However, you *can* loop both the ingress and egress traffic through a common IFB interface, and shape that - using Cake, even. That sounds like what you’re trying to experiment with.
>
> - Jonathan Morton
>
[-- Attachment #2: Type: text/html, Size: 2379 bytes --]
next prev parent reply other threads:[~2016-12-09 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 10:12 [Codel] " Phineas Gage
2016-12-09 11:39 ` [Codel] [Make-wifi-fast] " Jonathan Morton
2016-12-09 12:37 ` Phineas Gage [this message]
2016-12-11 11:54 ` Phineas Gage
2016-12-09 13:41 ` David Lang
2016-12-09 14:43 ` Phineas Gage
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5EA3C6E6-76C7-4347-9B14-3C310271A8FD@gmail.com \
--to=phineas919@gmail.com \
--cc=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--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