From: Hal Murray <hmurray@megapathdsl.net>
To: bloat@lists.bufferbloat.net
Cc: Hal Murray <hmurray@megapathdsl.net>
Subject: Re: [Bloat] bbr on slashdot
Date: Sat, 02 Nov 2019 16:38:33 -0700 [thread overview]
Message-ID: <20191102233833.79936406074@ip-64-139-1-69.sjc.megapath.net> (raw)
Sebastian Moeller said:
> Interestingly, the naive expectation in the vice text is equal sharing
> between all concurrent flows, if only we had a system that could actually
> help achieving this kind of set-up that is fair to each flow...
Is there consensus on what a flow is? Or what the unit of traffic that
fairness measures should be?
It seems to me that it depends on where you are located.
Consider upstream traffic:
If I'm a workstation or server, I probably want to give equal weight to each
connection.
If I'm an exit router at a residence, I probably want to give equal weight to
each IP Address. If not, pigs can game the system by making multiple
connections. But if I have a server, maybe I want to reserve or limit the
bandwidth it gets - reserve to keep the workstation/laptop traffic from
killing the server and limit so the workstation/laptop people can get some
work done when the server is busy.
If I'm an ISP customer facing router, I probably want to give equal weight to
each customer, probably scaled by how much bandwidth they are paying for.
I don't know how to handle backbone routers. You probably want to treat each
customer as a flow, again scaled by how much bandwidth they are paying for.
But an IP level packet doesn't tell you anything about which customer it came
from.
If this is old news, please point me at a good writeup.
--
These are my opinions. I hate spam.
next reply other threads:[~2019-11-02 23:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 23:38 Hal Murray [this message]
2019-11-02 23:44 ` Dave Taht
2019-11-03 11:14 ` Sebastian Moeller
-- strict thread matches above, loose matches on Subject: below --
2019-11-01 18:19 Dave Taht
2019-11-01 21:14 ` Sebastian Moeller
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191102233833.79936406074@ip-64-139-1-69.sjc.megapath.net \
--to=hmurray@megapathdsl.net \
--cc=bloat@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