From: Jonathan Morton <chromatix99@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Georgios Amanakis <gamanakis@gmail.com>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] dual-src/dsthost unfairness, only with bi-directional traffic
Date: Fri, 18 Jan 2019 15:45:12 +0200 [thread overview]
Message-ID: <2A195F4F-2F87-4742-93BE-273B5B8DB97D@gmail.com> (raw)
In-Reply-To: <87pnsu3xac.fsf@toke.dk>
>> Yes, exactly. Would be interesting to hear what Jonathan, Toke and
>> others think. I want to see if fairness is preserved in this case with
>> sparse flows only. Could flent do this?
>
> Well, sparse flows are (by definition) not building a queue, so it
> doesn't really make sense to talk about fairness for them. How would you
> measure that?
>
> This is also the reason I agree that they shouldn't be counted for host
> fairness calculation purposes, BTW...
The trick is that we need to keep fairness of the deficit replenishments, which occur for sparse flows as well as bulk ones, but in smaller amounts. The number of active flows is presently the stand-in for this. It's possible to have a host backlogged with hundreds of new flows which are, by definition, sparse.
I'm still trying to get my head around how the modified code works in detail. It's possible that a different implementation would either be more concise and readable, or better model what is actually needed. But I can't tell until I grok it.
- Jonathan Morton
next prev parent reply other threads:[~2019-01-18 13:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 23:04 Pete Heist
2019-01-03 3:57 ` Georgios Amanakis
2019-01-03 4:15 ` Georgios Amanakis
2019-01-03 5:18 ` Jonathan Morton
2019-01-03 10:46 ` Pete Heist
2019-01-03 11:03 ` Toke Høiland-Jørgensen
2019-01-03 13:02 ` Pete Heist
2019-01-03 13:20 ` Toke Høiland-Jørgensen
2019-01-03 16:35 ` Pete Heist
2019-01-03 18:24 ` Georgios Amanakis
2019-01-03 22:06 ` Pete Heist
2019-01-04 2:08 ` Georgios Amanakis
2019-01-04 8:09 ` Pete Heist
2019-01-04 7:37 ` Pete Heist
2019-01-04 11:34 ` Pete Heist
2019-01-15 19:22 ` George Amanakis
2019-01-15 22:42 ` Georgios Amanakis
2019-01-16 3:34 ` George Amanakis
2019-01-16 3:47 ` gamanakis
2019-01-16 7:58 ` Pete Heist
2019-01-26 7:35 ` Pete Heist
2019-01-28 1:34 ` Georgios Amanakis
2019-01-18 10:06 ` Toke Høiland-Jørgensen
2019-01-18 12:07 ` Georgios Amanakis
2019-01-18 13:33 ` Toke Høiland-Jørgensen
2019-01-18 13:40 ` Sebastian Moeller
2019-01-18 14:30 ` Toke Høiland-Jørgensen
2019-01-18 13:45 ` Jonathan Morton [this message]
2019-01-18 14:32 ` 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/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=2A195F4F-2F87-4742-93BE-273B5B8DB97D@gmail.com \
--to=chromatix99@gmail.com \
--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