From: Dong Mo <montedong@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] New to codel-- how to run codel on a linux box?
Date: Thu, 5 Dec 2013 13:36:54 -0600 [thread overview]
Message-ID: <CAAUsAoS==k1=H-Wq_p5Q-bXzcjycruvmU=5njEd_mV_gCKFV=w@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6JSC6xRgFHSrLZu_h82mNgCQPj8NCG6SiU2qL5zXBA4Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
Thanks for the reply and I think I have successfully set up codel.
Unfortunately I am also new to qdisc.
I am trying to compare fq_codel and sfq's performance. I was wondering how
to setup a software rate limiting using htb and at the same time have sfq
on this bottleneck link using qdisc.
Thank you so much!
-Mo
2013/11/23 Dave Taht <dave.taht@gmail.com>
> Why burst 15k? Quantum 1514 works for me.
>
> While htb will give the best results it is also the most CPU intensive.
>
> I also note that running it on ingress can be useful especially with ecn.
>
> IF you have a simple network driver with no ring buffer... Or you have
> working BQL... And you want to run at line rate at 100 Mbit... You can
> tell your Ethernet driver to switch to 100mbit via
>
> ethtool -s your device advertise 0x008
>
> See also caveats on tso etc:
>
>
> http://www.bufferbloat.net/projects/codel/wiki/Best_Practices_for_Benchmarking_CoDel_and_FQ_CoDel
> On Nov 23, 2013 2:26 AM, "Jonathan Morton" <chromatix99@gmail.com> wrote:
>
>>
>> On 23 Nov, 2013, at 7:04 am, Dong Mo wrote:
>>
>> > I am new to codel and I would like to run some experiments with codel
>> on a linux box acting as a router. I see on the wiki that running codel on
>> linux requires BQL support from NIC driver. I would like to know is this an
>> essential requirement to run codel on linux box or it is optional?
>>
>> It's not a hard requirement - but large hardware queues (which BQL tries
>> to solve) tend to interfere with line-rate operation.
>>
>> > I don't require line rate performance, something like 100Mbps
>> throughput will be enough for the experiment. However, It is also not clear
>> to me that how Codel is going to interact with some software traffic
>> shaping say bandwidth limiting?
>>
>> tc qdisc add dev $IFACE root handle 1: htb default 1
>> tc class add dev $IFACE parent 1: classid 1:1 htb rate $RATE burst 15k
>> tc qdisc add dev $IFACE parent 1:1 handle 10: fq_codel
>>
>> That works perfectly well if $RATE is less than line rate, even without
>> BQL.
>>
>> - Jonathan Morton
>>
>> _______________________________________________
>> Codel mailing list
>> Codel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/codel
>>
>
[-- Attachment #2: Type: text/html, Size: 3319 bytes --]
next prev parent reply other threads:[~2013-12-05 19:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 5:04 Dong Mo
2013-11-23 10:23 ` Jonathan Morton
2013-11-23 14:43 ` Dave Taht
2013-12-05 19:36 ` Dong Mo [this message]
2013-12-05 19:49 ` Dong Mo
2013-12-05 20:06 ` Jonathan Morton
2013-12-05 20:21 ` Dong Mo
2013-12-05 21:03 ` Toke Høiland-Jørgensen
2013-12-05 22:29 ` Dong Mo
2013-12-05 23:25 ` Toke Høiland-Jørgensen
2013-12-05 23:28 ` Dong Mo
2013-12-05 23:43 ` Toke Høiland-Jørgensen
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='CAAUsAoS==k1=H-Wq_p5Q-bXzcjycruvmU=5njEd_mV_gCKFV=w@mail.gmail.com' \
--to=montedong@gmail.com \
--cc=codel@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