From: Sebastian Moeller <moeller0@gmx.de>
To: leetminiwheat <LeetMiniWheat@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] squash/ignore DSCP and mangle table questions
Date: Wed, 15 Apr 2015 11:05:31 +0200 [thread overview]
Message-ID: <B65E75F4-C2DC-4906-8163-7F393EB88CE9@gmx.de> (raw)
In-Reply-To: <CAGHZhqFJL+s86RdwXAQADfYwrCnMLU4KesV4+es2p6NwSTzq5w@mail.gmail.com>
Hi leetminiwheat,
On Apr 15, 2015, at 03:35 , leetminiwheat <LeetMiniWheat@gmail.com> wrote:
> On Mon, Apr 13, 2015 at 5:39 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
>> This looks reasonable.
>>
>>> [...]
>>
>> I had a look at my cerowrt router and I also see txqueuelen at 1000, but IIRC that does not matter much anymore, since the wndr37/800 support BQL:
>> cat /sys/class/net/ge00/queues/tx-0/byte_queue_limits/limit_max
>> 3000
>> So even with txqueuelen = 1000 the tx queue will only hold 3000 bytes. For fib and friends it does not really matter as far as I can tell.
>
> Interesting, I had been reading about BQL but didn't fully understand
> it until now. This clears up a lot of confusion, thank you.
>
> I assume tweaking ring parameters from default RX:128 and TX:32
> doesn't matter anymore thenr?
As far as I know we leave that alone, see: http://www.bufferbloat.net/projects/bloat/wiki/Linux_Tips:
“Set the size of the ring buffer for the network interface
NOTE: THIS HACK IS NO LONGER NEEDED on many ethernet drivers in Linux 3.3, which has Byte Queue Limits instead, which does a far better job."
>
>> [...]
>> If you have time and netperf-wrapper it would be good to convince yourself and us again, that txqueuelen really does not matter for BQL’d interfaces by running RRUL tests with and without your modifications….
>
> Will do if I can get a friend to set up a netperf server in a node at
> his datacenter he works at, though I believe he's using Debian Jessy
> without any kind of QoS, but his datacenter routers might screw with
> the packets. Maybe I can hook a spare box up to the WAN port
> temporarily to test with.
Ah, there are three netperf servers out there that, as far as I know, we are allowed to use:
netperf-west.bufferbloat.net
netperf-east.bufferbloat.net
netperf-eu.bufferbloat.net
My guess is the last one should be closest to you, and should do at least for initial tests. Having a faster closer netperf server available certainly is even more attractive.
Best Regards
Sebastian
next prev parent reply other threads:[~2015-04-15 9:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 6:37 leetminiwheat
2015-04-13 7:36 ` Sebastian Moeller
2015-04-13 10:27 ` leetminiwheat
2015-04-13 10:36 ` leetminiwheat
[not found] ` <ECC39EB0-9C54-4C17-9285-2484AD08ACF3@gmx.de>
2015-04-13 13:43 ` leetminiwheat
2015-04-13 14:16 ` leetminiwheat
2015-04-13 14:23 ` Sebastian Moeller
2015-04-13 16:48 ` leetminiwheat
2015-04-13 21:39 ` Sebastian Moeller
2015-04-15 1:35 ` leetminiwheat
2015-04-15 9:05 ` Sebastian Moeller [this message]
2015-04-22 0:19 ` leetminiwheat
2015-04-22 0:28 ` leetminiwheat
2015-04-22 9:19 ` Sebastian Moeller
2015-04-22 9:03 ` Sebastian Moeller
2015-04-22 10:17 ` leetminiwheat
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B65E75F4-C2DC-4906-8163-7F393EB88CE9@gmx.de \
--to=moeller0@gmx.de \
--cc=LeetMiniWheat@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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