From: Sebastian Moeller <moeller0@gmx.de>
To: cake@lists.bufferbloat.net, Pete Heist <pete@heistp.net>,
George Amanakis <gamanakis@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Upstream submission of dual-mode fairness patch
Date: Sun, 03 Mar 2019 10:53:23 +0100 [thread overview]
Message-ID: <417E17B2-17F7-4106-A92D-C5B5AC41D808@gmx.de> (raw)
In-Reply-To: <ECB616A2-A21A-44B3-8150-94C8DDFDFABF@heistp.net>
[-- Attachment #1: Type: text/plain, Size: 2342 bytes --]
Mmmh,
Doesn't this look like ingress magic being applied selectively to the users based on number of flows? I thought that the idea behind the ingress keyword is to effectively shape harder the more bulk flows are coming in.
Just asking...
Best regards
Sebastian
On March 3, 2019 8:19:00 AM GMT+01:00, Pete Heist <pete@heistp.net> wrote:
>Oops, sorry I didn’t notice this before but it’s the ingress keyword
>that makes the difference:
>
>qdisc cake 802c: dev ifbLink2 parent 1:1 bandwidth unlimited besteffort
>dual-dsthost nonat nowash ingress no-ack-filter no-split-gso rtt
>100.0ms raw overhead 0
>
>IP1, 1 up: 46.8 Mbit
>IP2, 16 up: 46.8 Mbit
>IP1, 16 down: 41.9 Mbit
>IP2, 1 down: 51.1 Mbit
>
>qdisc cake 803a: dev ifbLink2 parent 1:1 bandwidth unlimited besteffort
>dual-dsthost nonat nowash no-ack-filter no-split-gso rtt 100.0ms raw
>overhead 0
>
>IP1, 1 up: 46.6 Mbit
>IP2, 16 up: 46.5 Mbit
>IP1, 16 down: 46.4 Mbit
>IP2, 1 down: 46.5 Mbit
>
>Also, my setup is different in that I use cake as a leaf to either hfsc
>or htb. But, it’s adding the ingress keyword that causes the imbalance
>for me.
>
>> On Mar 2, 2019, at 11:20 AM, Pete Heist <pete@heistp.net> wrote:
>>
>> Great, thanks for trying it. That strongly suggests a problem with
>the kernel (or driver) I’m using. Feels better to know it works as it
>should in recent kernels though...
>>
>>> On Mar 2, 2019, at 5:47 AM, George Amanakis <gamanakis@gmail.com>
>wrote:
>>>
>>> On Fri, 2019-03-01 at 22:02 -0500, George Amanakis wrote:
>>>>
>>>> I will setup a vlan and try again.
>>>>
>>>
>>> I replicated Pete's VLAN setup, and I am getting fairness:
>>>
>>> IP1,2 <---> router enp1s0 / router enp1s0.100 <---> server
>>>
>>> IP1, 1 up: 46.73 mbit/s
>>> IP2, 32 up: 46.91
>>> IP1, 32 down: 46.70
>>> IP2, 1 down: 46.89
>>>
>>> qdisc cake 8006: dev enp1s0.100 root refcnt 2 bandwidth 100Mbit
>>> diffserv3 dual-srchost nonat nowash no-ack-filter split-gso nofwmark
>>> rtt 100.0ms noatm overhead 4
>>>
>>> qdisc cake 8002: dev ifb0 root refcnt 2 bandwidth 100Mbit diffserv3
>>> dual-dsthost nonat nowash no-ack-filter split-gso nofwmark rtt
>100.0ms
>>> noatm overhead 4
>>>
>>>
>>>
>>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 3965 bytes --]
next prev parent reply other threads:[~2019-03-03 9:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1788.1551352661.3538.cake@lists.bufferbloat.net>
2019-03-01 10:52 ` Pete Heist
2019-03-01 11:01 ` Toke Høiland-Jørgensen
2019-03-01 11:55 ` Pete Heist
2019-03-01 14:40 ` Georgios Amanakis
2019-03-01 16:43 ` Pete Heist
2019-03-02 3:02 ` George Amanakis
2019-03-02 4:47 ` George Amanakis
2019-03-02 10:20 ` Pete Heist
2019-03-03 7:19 ` Pete Heist
2019-03-03 9:53 ` Sebastian Moeller [this message]
2019-03-03 9:58 ` Jonathan Morton
2019-03-03 11:26 ` Sebastian Moeller
2019-03-03 12:13 ` Jonathan Morton
2019-03-03 12:53 ` Sebastian Moeller
2019-03-03 16:07 ` Pete Heist
2019-03-03 16:10 ` Jonathan Morton
2019-03-03 16:35 ` Pete Heist
2019-03-03 16:40 ` Jonathan Morton
2019-03-03 18:48 ` Pete Heist
2019-03-03 19:03 ` gamanakis
2019-03-03 19:49 ` Pete Heist
2019-03-04 2:55 ` Georgios Amanakis
2019-03-04 3:17 ` Jonathan Morton
2019-03-04 4:22 ` Ryan Mounce
2019-03-04 8:27 ` Pete Heist
2019-03-04 13:17 ` Pete Heist
2019-03-04 14:36 ` Georgios Amanakis
2019-03-03 12:06 ` Pete Heist
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=417E17B2-17F7-4106-A92D-C5B5AC41D808@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=gamanakis@gmail.com \
--cc=pete@heistp.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