From: Alessandro Bolletta <alessandro@mediaspot.net>
To: "Codel@lists.bufferbloat.net" <Codel@lists.bufferbloat.net>
Subject: [Codel] fq_codel and 802.11n packet aggregation
Date: Mon, 24 Dec 2012 10:17:33 +0000 [thread overview]
Message-ID: <F52F175DFC537F48A43937B50B44BCA276D0D9A5@EXCHANGE.mediaspot.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 3495 bytes --]
next reply other threads:[~2012-12-24 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 10:17 Alessandro Bolletta [this message]
2012-12-24 12:15 ` Andrew McGregor
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=F52F175DFC537F48A43937B50B44BCA276D0D9A5@EXCHANGE.mediaspot.local \
--to=alessandro@mediaspot.net \
--cc=Codel@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