From: Pete Heist <pete@heistp.net>
To: George Amanakis <gamanakis@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Upstream submission of dual-mode fairness patch
Date: Sun, 3 Mar 2019 13:06:34 +0100 [thread overview]
Message-ID: <EE1937D8-FC71-466E-B66F-388802A3FFB2@heistp.net> (raw)
In-Reply-To: <ECB616A2-A21A-44B3-8150-94C8DDFDFABF@heistp.net>
[-- Attachment #1: Type: text/plain, Size: 2990 bytes --]
As another clue, the un-fairness goes away when ECN is enabled on the client (both results with ingress keyword in use):
sysctl -w net.ipv4.tcp_ecn=2
IP1, 1 up: 46.7 Mbit
IP2, 16 up: 46.7 Mbit
IP1, 16 down: 41.0 Mbit
IP2, 1 down: 49.3 Mbit
sysctl -w net.ipv4.tcp_ecn=1
IP1, 1 up: 47.0 Mbit
IP2, 16 up: 47.0 Mbit
IP1, 16 down: 46.1 Mbit
IP2, 1 down: 46.1 Mbit
Also, this is probably just academic, but here are pcaps of "IP1, 16 down", with and without “ingress” and ECN enabled, along with some throughput and RTT graphs of one of the 16 flows for each: https://www.heistp.net/downloads/ingress_fairness/ <https://www.heistp.net/downloads/ingress_fairness/>
I find the different TCP RTT “slots” interesting (see the rtt graphs, all times in ms):
no ingress: 4, 8.5, 13, 17
no ingress+ecn: 8, 12, 16 (a few outliers at 20)
ingress: 4, 8, 12, 16, 20
ingress+ecn: 8, 12, 16 (outliers at 4 and 20 later in test)
> On Mar 3, 2019, at 8:19 AM, 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 <mailto: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 <mailto: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
>>>
>>>
>>>
>>
>
[-- Attachment #2: Type: text/html, Size: 5354 bytes --]
prev parent reply other threads:[~2019-03-03 12:06 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
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 [this message]
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=EE1937D8-FC71-466E-B66F-388802A3FFB2@heistp.net \
--to=pete@heistp.net \
--cc=cake@lists.bufferbloat.net \
--cc=gamanakis@gmail.com \
--cc=toke@redhat.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