From: Dan Siemon <dan@coverfire.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: bloat <bloat@lists.bufferbloat.net>,
Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [Bloat] curious.....
Date: Sat, 21 Dec 2013 20:38:41 -0500 [thread overview]
Message-ID: <1387676321.2098.4.camel@ganymede.home> (raw)
In-Reply-To: <15B33C3B-4F1D-4CC6-AC24-CA8926047D38@gmx.de>
On Sun, 2013-12-08 at 20:02 +0100, Sebastian Moeller wrote:
> About prioritizing, I am less optimistic as I can not see how the system can behave well under extreme load; I for one would be quite unhappy if an device on my internal network could effectively DOS my ability to make phone calls (I switched to IP telephony so this theoretical issue has become practical for me).
> Or put it that way, I hope that the core internet is over-provided and will not cause congestion, at the same time I want to be able to max out my internet connection and still be able to phone.
Making it impossible for an internal host to DOS VoIP quality is one of
the reasons I've been playing with per host fairness in addition to
three priority levels (per host). The tc script is below with a link to
performance results.
http://git.coverfire.com/?p=linux-qos-scripts.git;a=blob;f=src-3tos.sh;hb=HEAD
next prev parent reply other threads:[~2013-12-22 1:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 18:40 Outback Dingo
2013-12-03 22:25 ` Kenyon Ralph
2013-12-04 0:25 ` Outback Dingo
2013-12-04 0:38 ` Dave Taht
2013-12-06 17:19 ` Juliusz Chroboczek
2013-12-06 18:15 ` Dave Taht
2013-12-07 11:24 ` Sebastian Moeller
2013-12-10 19:05 ` Dave Taht
2013-12-11 10:44 ` Sebastian Moeller
2013-12-07 12:59 ` Juliusz Chroboczek
2013-12-08 1:27 ` Steinar H. Gunderson
2013-12-08 5:24 ` Mikael Abrahamsson
2013-12-08 11:00 ` Mark Constable
2013-12-08 14:01 ` Outback Dingo
2013-12-08 14:03 ` Outback Dingo
2013-12-08 16:44 ` Mark Constable
2013-12-08 19:00 ` Sebastian Moeller
2013-12-08 13:12 ` Juliusz Chroboczek
2013-12-08 16:46 ` Jonathan Morton
2013-12-08 16:51 ` Dave Taht
2013-12-08 17:56 ` Juliusz Chroboczek
2013-12-08 21:05 ` Jonathan Morton
2013-12-08 14:22 ` Aaron Wood
2013-12-08 14:41 ` Jim Gettys
2013-12-08 10:40 ` Sebastian Moeller
2013-12-08 13:25 ` Juliusz Chroboczek
2013-12-08 16:26 ` Sebastian Moeller
2013-12-08 17:47 ` Juliusz Chroboczek
2013-12-08 19:02 ` Sebastian Moeller
2013-12-22 1:38 ` Dan Siemon [this message]
2013-12-22 3:46 ` Stephen Hemminger
2013-12-08 19:01 ` Jonathan Morton
2013-12-08 19:21 ` Sebastian Moeller
2013-12-08 16:01 ` Neil Davies
2013-12-08 20:41 Hal Murray
2013-12-08 23:16 ` Stephen Hemminger
2013-12-09 9:51 ` 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=1387676321.2098.4.camel@ganymede.home \
--to=dan@coverfire.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jch@pps.univ-paris-diderot.fr \
--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