<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://2910/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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">alessandro@mediaspot.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="IT" link="#0563C1" vlink="#954F72" 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-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Hi everybody,<o:p></o:p></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.<o:p></o:p></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.<o:p></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></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.<o:p></o:p></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.<o:p></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></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.<o:p></o:p></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?<o:p></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Thanks so much for your help!<o:p></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Alessandro<o:p></o:p></div></div>_______________________________________________<br>Codel mailing list<br><a href="mailto:Codel@lists.bufferbloat.net" style="color: rgb(149, 79, 114); text-decoration: underline; ">Codel@lists.bufferbloat.net</a><br><a href="https://lists.bufferbloat.net/listinfo/codel" style="color: rgb(149, 79, 114); text-decoration: underline; ">https://lists.bufferbloat.net/listinfo/codel</a><br></div></blockquote></div><br></div></body></html>