From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: moeller0 <moeller0@gmx.de>, cake@lists.bufferbloat.net
Subject: Re: [Cake] triple flow isolation
Date: Mon, 18 Jan 2016 11:08:25 +0000 [thread overview]
Message-ID: <CANmMgnHik_pYSMTXyQZ-ao8MaY5=ZecLAH0=W2U_AW2Wgy1gjg@mail.gmail.com> (raw)
In-Reply-To: <72B1E8E5-F42D-4B13-A404-5DE82F8658F9@gmail.com>
On 18/01/2016, Jonathan Morton <chromatix99@gmail.com> wrote:
> Hence I think it’s reasonable to simply switch on triple isolation by
> default, in the near future. It does approximately the right thing, without
> further configuration, in the great majority of practical cases (that I can
> think of), and to a greater extent than the existing “flows” mode does.
A question from complete ignorance of this feature:
Do you prioritize by app ("traffic class") before imposing host
fairness, or vice versa?
We have these rules that voice, or video, can get special treatment in
order to survive (but aren't allowed to monopolize the connection).
If two local hosts simply cut the connection in half, we kind of lose
that prioritization.
E.g. when I was sharing with 4 other students - I want my house-mates
bittorrenting to stay firmly in the scavenger class when I want to use
the internet :). (And vice-versa; I want to be able to leave my
bittorrent on and not get shouted at because netflix cuts out and
downgrades to standard definition).
Alan
next prev parent reply other threads:[~2016-01-18 11:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 17:40 Kevin Darbyshire-Bryant
2016-01-11 18:16 ` moeller0
2016-01-11 20:33 ` Kevin Darbyshire-Bryant
2016-01-14 14:20 ` moeller0
2016-01-14 14:45 ` Jonathan Morton
2016-01-14 15:48 ` moeller0
2016-01-14 16:05 ` Jonathan Morton
[not found] ` <02A10F37-145C-4BF9-B428-BC1BDF700135@gmx.de>
2016-01-15 0:05 ` Jonathan Morton
2016-01-15 8:05 ` moeller0
2016-01-16 9:05 ` Jonathan Morton
2016-01-16 9:35 ` Jonathan Morton
2016-01-17 22:22 ` moeller0
2016-01-18 9:21 ` moeller0
2016-01-18 9:37 ` Jonathan Morton
2016-01-18 11:08 ` Alan Jenkins [this message]
2016-01-18 11:39 ` Jonathan Morton
2016-01-18 16:20 ` 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/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='CANmMgnHik_pYSMTXyQZ-ao8MaY5=ZecLAH0=W2U_AW2Wgy1gjg@mail.gmail.com' \
--to=alan.christopher.jenkins@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=moeller0@gmx.de \
/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