From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] curious.....
Date: Sat, 07 Dec 2013 13:59:04 +0100 [thread overview]
Message-ID: <87haakx1ev.wl%jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <CAA93jw4XfSuoeB=eR2DKRHLOsXx8Ng8j9i_29pDQ4Soo6BvNrQ@mail.gmail.com>
> > Perhaps you should push your system to OpenWRT?
> There is still some work going on to streamline the gui.
Fair enough. That's important.
> there are less features in the aqm-scripts for prioritizing packet
> types than qos-scripts.
I wouldn't bother much with that. The promise of fq_codel is that we
can get rid of our prioritising hacks -- if we need that kind of
features, then fq_codel has failed.
> I just had to come up with a way to disable it at high (> 80 mbit)
> rates on incoming traffic (not enough cpu in cerowrt),
I wouldn't bother with that either. 120 Mbit/s is the highest rate you
can get in Europe as far as I can tell, so being able to push 80 Mbit/s
on a four year old router is fine (as long as you're careful to avoid
shaping traffic between LAN and WLAN -- I certainly wouldn't want
backing up my laptop to be capped at 80 Mbit/s).
> so I'd like it to run faster, maybe using drr in that case, or
> something like what free.fr uses...
What are they using?
> And there are actually two aqm/packet scheduling shapers in there (a
> simple 1 tier and a 3 tier one),
Remove the non-default features. Be a man, Dave, dump it all.
> In the interim, existing openwrt users can add ceropackages-3.3 into
> their feeds.
They won't. If you want to have an effect on the world, you need to
push it into the default OpenWRT scripts.
-- Juliusz
next prev parent reply other threads:[~2013-12-07 12:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 18:40 Outback Dingo
2013-12-03 22:25 ` Kenyon Ralph
2013-12-04 0:25 ` Outback Dingo
2013-12-04 0:38 ` Dave Taht
2013-12-06 17:19 ` Juliusz Chroboczek
2013-12-06 18:15 ` Dave Taht
2013-12-07 11:24 ` Sebastian Moeller
2013-12-10 19:05 ` Dave Taht
2013-12-11 10:44 ` Sebastian Moeller
2013-12-07 12:59 ` Juliusz Chroboczek [this message]
2013-12-08 1:27 ` Steinar H. Gunderson
2013-12-08 5:24 ` Mikael Abrahamsson
2013-12-08 11:00 ` Mark Constable
2013-12-08 14:01 ` Outback Dingo
2013-12-08 14:03 ` Outback Dingo
2013-12-08 16:44 ` Mark Constable
2013-12-08 19:00 ` Sebastian Moeller
2013-12-08 13:12 ` Juliusz Chroboczek
2013-12-08 16:46 ` Jonathan Morton
2013-12-08 16:51 ` Dave Taht
2013-12-08 17:56 ` Juliusz Chroboczek
2013-12-08 21:05 ` Jonathan Morton
2013-12-08 14:22 ` Aaron Wood
2013-12-08 14:41 ` Jim Gettys
2013-12-08 10:40 ` Sebastian Moeller
2013-12-08 13:25 ` Juliusz Chroboczek
2013-12-08 16:26 ` Sebastian Moeller
2013-12-08 17:47 ` Juliusz Chroboczek
2013-12-08 19:02 ` Sebastian Moeller
2013-12-22 1:38 ` Dan Siemon
2013-12-22 3:46 ` Stephen Hemminger
2013-12-08 19:01 ` Jonathan Morton
2013-12-08 19:21 ` Sebastian Moeller
2013-12-08 16:01 ` Neil Davies
2013-12-08 20:41 Hal Murray
2013-12-08 23:16 ` Stephen Hemminger
2013-12-09 9:51 ` Sebastian Moeller
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87haakx1ev.wl%jch@pps.univ-paris-diderot.fr \
--to=jch@pps.univ-paris-diderot.fr \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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