<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" style="word-wrap:break-word">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Now I understand... I also tried to find out more specific causes for this problem and I found them on Cerowrt wiki.<br>
<br>
Unfortunately, i'm not a networking programmer and I can't offer my (direct) support to the project, but I will give my effort into trying to find out resources that could be helpful in order to fix this bug.<br>
<br>
As David described in his article on wiki: "It bugs us that there are million activations of android a month with a wifi stack that can be so dramatically improved by a variety of queue management techniques - and 10s of millions of APs and 100s of millions
of deployed wifi devices, all with problems -"<br>
<br>
I totally agree with his thought. I hope to find a way to help fq_codel's development in the future.<br>
<br>
Thanks<br>
<br>
Alessandro Bolletta<br>
<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF617438"><font color="#000000" face="Tahoma" size="2"><b>Da:</b> Andrew McGregor [andrewmcgr@gmail.com]<br>
<b>Inviato:</b> lunedì 24 dicembre 2012 13.15<br>
<b>A:</b> Alessandro Bolletta<br>
<b>Cc:</b> Codel@lists.bufferbloat.net<br>
<b>Oggetto:</b> Re: [Codel] fq_codel and 802.11n packet aggregation<br>
</font><br>
</div>
<div></div>
<div>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.
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Andrew</div>
<div><br>
<div>
<div>On 24/12/2012, at 11:17 PM, Alessandro Bolletta <<a href="mailto:alessandro@mediaspot.net" target="_blank">alessandro@mediaspot.net</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-family:'Lucida Sans'; font-size:medium; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:2; text-indent:0px; text-transform:none; white-space:normal; widows:2; word-spacing:0px" lang="IT">
<div class="WordSection1" style="">
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
Hi everybody,</div>
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
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.</div>
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
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.</div>
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</div>
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
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.</div>
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
Also, I could increase target and interval values whenever i’ll need to adjust settings that I can’t expect now.</div>
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</div>
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
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.</div>
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
What do you think about? Is it a good compromise or there are other aspects that i’m leaving behind?</div>
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</div>
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
Thanks so much for your help!</div>
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
</div>
<div style="margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
Alessandro</div>
</div>
_______________________________________________<br>
Codel mailing list<br>
<a href="mailto:Codel@lists.bufferbloat.net" style="color:rgb(149,79,114); text-decoration:underline" target="_blank">Codel@lists.bufferbloat.net</a><br>
<a href="https://lists.bufferbloat.net/listinfo/codel" style="color:rgb(149,79,114); text-decoration:underline" target="_blank">https://lists.bufferbloat.net/listinfo/codel</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</body>
</html>