Anyone know what the situation is with kirkwood and BQL? I found a
patch for it but have no idea if there are any issues.
I have such a system but have no idea how to ascertain the efficacy of BQL.
___
Bloat mailing list
Bloat@lists.bufferbloat.net
https
On 28/07/15 21:10, Alan Jenkins wrote:
On 28/07/15 20:24, Juliusz Chroboczek wrote:
I would be very interested in flent benchmarks of your 3g device with
the 3 packet txqueue and with fq_codel, for the tcp_upload, rrul, and
rrul_be tests.
Please send me detailed instructions, as well as informa
On 28/07/15 20:24, Juliusz Chroboczek wrote:
I would be very interested in flent benchmarks of your 3g device with
the 3 packet txqueue and with fq_codel, for the tcp_upload, rrul, and
rrul_be tests.
Please send me detailed instructions, as well as information about how
much traffic I'm going to
It sounds like (one or more ) interface upstream of your link is also subject
to periodic congestion. What a shocker --- cascaded links subject to bloat.
Bvs
-Original Message-
From: bloat-boun...@lists.bufferbloat.net
[mailto:bloat-boun...@lists.bufferbloat.net] On Behalf Of Juliusz C
On 28/07/15 20:20, Juliusz Chroboczek wrote:
Debian. (One machine stable, one testing.)
Right. Don't know if there's already an effort to convince the Debian
devs to switch the default...
Please file a bug against the procps package (which owns the sysctl.conf
file). Just send a mail describi
> I would be very interested in flent benchmarks of your 3g device with
> the 3 packet txqueue and with fq_codel, for the tcp_upload, rrul, and
> rrul_be tests.
Please send me detailed instructions, as well as information about how
much traffic I'm going to have to pay for.
FWIW, the RTT of the (
>> Debian. (One machine stable, one testing.)
> Right. Don't know if there's already an effort to convince the Debian
> devs to switch the default...
Please file a bug against the procps package (which owns the sysctl.conf
file). Just send a mail describing the issue and the proposed fix to
sub
> On 28. jul. 2015, at 18.22, Sebastian Moeller wrote:
>
> Hi Simon,
>
> On Jul 28, 2015, at 16:31 , Simon Barber wrote:
>
>> The issue is that Codel tries to keep the delay low, and will start dropping
>> when sojourn time grows above 5ms for 100ms. For longer RTT links more delay
>> is ne
Hi Simon,
On Jul 28, 2015, at 16:31 , Simon Barber wrote:
> The issue is that Codel tries to keep the delay low, and will start dropping
> when sojourn time grows above 5ms for 100ms. For longer RTT links more delay
> is necessary to avoid underutilizing the link. This is due to the
> multipl
On 28/07/15 15:49, Eric Dumazet wrote:
On Tue, 2015-07-28 at 07:31 -0700, Simon Barber wrote:
The issue is that Codel tries to keep the delay low, and will start
dropping when sojourn time grows above 5ms for 100ms. For longer RTT links
more delay is necessary to avoid underutilizing the link. T
On Tue, 2015-07-28 at 16:49 +0200, Eric Dumazet wrote:
> On Tue, 2015-07-28 at 07:31 -0700, Simon Barber wrote:
> > The issue is that Codel tries to keep the delay low, and will start
> > dropping when sojourn time grows above 5ms for 100ms. For longer RTT links
> > more delay is necessary to avo
On Tue, 2015-07-28 at 16:44 +0200, Dave Taht wrote:
>
> 4) setting the default qdisc to be fq_codel in the sysctl works on
> most dynamically created devices, but does not work on devices that
> come up at boot time before the sysctls have a chance to run and the
> modprobes to complete. This is
On Tue, 2015-07-28 at 07:31 -0700, Simon Barber wrote:
> The issue is that Codel tries to keep the delay low, and will start
> dropping when sojourn time grows above 5ms for 100ms. For longer RTT links
> more delay is necessary to avoid underutilizing the link. This is due to
> the multiplicativ
On Tue, Jul 28, 2015 at 3:09 PM, Juliusz Chroboczek
wrote:
> I'm currently away from home, and using a 3G modem for Internet access.
> I've found out that both NetworkManager and wvdial/pppd setup the
> interface to use pfifo_fast (with a qlen of a mere 3 packets!). Setting
> fq_codel manually ap
> On 28 Jul, 2015, at 17:31, Simon Barber wrote:
>
> The issue is that Codel tries to keep the delay low, and will start dropping
> when sojourn time grows above 5ms for 100ms. For longer RTT links more delay
> is necessary to avoid underutilizing the link.
I’m pretty sure we’ve had this disc
The issue is that Codel tries to keep the delay low, and will start
dropping when sojourn time grows above 5ms for 100ms. For longer RTT links
more delay is necessary to avoid underutilizing the link. This is due to
the multiplicative decrease - it's worst with Reno, where the halving of
cWind
On Tue, 2015-07-28 at 07:11 -0700, Simon Barber wrote:
> The main danger is the negative effects on performance of using Codel. You
> may experience low throughput on high RTT links.
Really ? I've never seen this, unless you mess with codel qdisc
attributes maybe.
(Some guys seem to not really u
On Tue, 2015-07-28 at 15:50 +0200, Juliusz Chroboczek wrote:
> > What distro are you on?
>
> Debian. (One machine stable, one testing.)
>
> > There's a sysctl to set the default qdisc: net.core.default_qdisc.
>
> $ sysctl -a | grep default_qdisc
> net.core.default_qdisc = pfifo_fast
>
The main danger is the negative effects on performance of using Codel. You
may experience low throughput on high RTT links.
Simon
Sent with AquaMail for Android
http://www.aqua-mail.com
On July 28, 2015 7:06:22 AM Toke Høiland-Jørgensen wrote:
Juliusz Chroboczek writes:
>> What distro ar
Juliusz Chroboczek writes:
>> What distro are you on?
>
> Debian. (One machine stable, one testing.)
Right. Don't know if there's already an effort to convince the Debian
devs to switch the default...
>> Set this to fq_codel and you should be good to go.
>
> Is that safe? I'm thinking lo and
> What distro are you on?
Debian. (One machine stable, one testing.)
> There's a sysctl to set the default qdisc: net.core.default_qdisc.
$ sysctl -a | grep default_qdisc
net.core.default_qdisc = pfifo_fast
> Set this to fq_codel and you should be good to go.
Is that safe? I'm thinki
Juliusz Chroboczek writes:
> I'm currently away from home, and using a 3G modem for Internet
> access. I've found out that both NetworkManager and wvdial/pppd setup
> the interface to use pfifo_fast (with a qlen of a mere 3 packets!).
> Setting fq_codel manually appears to work fine, but needs to
I'm currently away from home, and using a 3G modem for Internet access.
I've found out that both NetworkManager and wvdial/pppd setup the
interface to use pfifo_fast (with a qlen of a mere 3 packets!). Setting
fq_codel manually appears to work fine, but needs to be redone every time
the modem has
23 matches
Mail list logo
