From: Andrew McGregor <andrewmcgr@gmail.com>
To: Alessandro Bolletta <alessandro@mediaspot.net>
Cc: "Codel@lists.bufferbloat.net" <Codel@lists.bufferbloat.net>
Subject: Re: [Codel] fq_codel and 802.11n packet aggregation
Date: Tue, 25 Dec 2012 01:15:49 +1300 [thread overview]
Message-ID: <8674C071-D403-4221-B2AA-535ECC8208F3@gmail.com> (raw)
In-Reply-To: <F52F175DFC537F48A43937B50B44BCA276D0D9A5@EXCHANGE.mediaspot.local>
[-- Attachment #1.1: Type: text/plain, Size: 2020 bytes --]
You don't ever want to increase either target or interval... in fact, leaving interval completely alone and slightly reducing target is all you should do.
fq_codel suffers a little on wireless... but to be sure, it isn't bad, it is still a vast improvement on basically anything else, it simply isn't quite optimal for that environment.
As to how long it will take to get this sorted, I don't think anyone will know for a month or two... but that might be all it takes.
Andrew
On 24/12/2012, at 11:17 PM, Alessandro Bolletta <alessandro@mediaspot.net> wrote:
> Hi everybody,
> thanks to Dave, I just learned that fq_codel suffers from every type of queuing technique made on underlaying layers (as in device drivers, for example), and one of these queuing techniques are 802.11n/ac packet aggregation and 802.11e QoS.
> David said that, at this time, the problem isn’t going to be solved shortly, even if it seems that there are already some ideas in order to solve this problem.
>
> In my specific case, I would like to run fq_codel in a new (and very extended) mesh network that doesn’t match with some limitations; for example, if it will occur that a link bandwidth falls below 4Mbit/s, mesh net will consider that link not available to carry traffic, because I surely know that it will not be sufficient to suit bandwidth requirements of my network.
> Also, I could increase target and interval values whenever i’ll need to adjust settings that I can’t expect now.
>
> So, i was thinking that, maybe, if i increase target and interval values to include packet aggregation delay times in the overall delay, I could just overall the problem, waiting for a fix in the future.
> What do you think about? Is it a good compromise or there are other aspects that i’m leaving behind?
>
> Thanks so much for your help!
>
> Alessandro
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
[-- Attachment #1.2: Type: text/html, Size: 4556 bytes --]
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2326 bytes --]
next prev parent reply other threads:[~2012-12-24 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 10:17 Alessandro Bolletta
2012-12-24 12:15 ` Andrew McGregor [this message]
2012-12-25 0:57 ` [Codel] R: " Alessandro Bolletta
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=8674C071-D403-4221-B2AA-535ECC8208F3@gmail.com \
--to=andrewmcgr@gmail.com \
--cc=Codel@lists.bufferbloat.net \
--cc=alessandro@mediaspot.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