From: Jonathan Morton <chromatix99@gmail.com>
To: Phineas Gage <phineas919@gmail.com>
Cc: codel@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Software rate limiting with fq_codel for point-to-point WiFi backhaul links
Date: Fri, 9 Dec 2016 13:39:58 +0200 [thread overview]
Message-ID: <EB6A0AC3-908A-4E80-8283-E31CFC1C1483@gmail.com> (raw)
In-Reply-To: <9BA0F7D8-5A25-4033-A101-38BF001B74EB@gmail.com>
> 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
next prev parent reply other threads:[~2016-12-09 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 10:12 Phineas Gage
2016-12-09 11:39 ` Jonathan Morton [this message]
2016-12-09 12:37 ` Phineas Gage
2016-12-11 11:54 ` Phineas Gage
2016-12-09 13:41 ` David Lang
2016-12-09 14:04 ` Jeremy Harris
2016-12-09 14:20 ` David Lang
2016-12-09 14:37 ` Jeremy Harris
2016-12-09 14:43 ` Phineas Gage
2016-12-09 15:47 ` Noah Causin
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=EB6A0AC3-908A-4E80-8283-E31CFC1C1483@gmail.com \
--to=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=phineas919@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