From: "George B." <georgeb@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] What is fairness, anyway? was: Re: finally... winning on wired!
Date: Sat, 4 Feb 2012 17:57:20 -0800 [thread overview]
Message-ID: <CAJ2iOjSmEG84DTKTurh_fKVWEmdKuUDL8jN=YKYhyEvMCXWFKg@mail.gmail.com> (raw)
In-Reply-To: <40C8C302-7B23-4272-8322-1D916BB0CEB2@gmail.com>
On Sat, Feb 4, 2012 at 4:43 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
> There are two good things you can do.
>
> 1) Pressure your ISP to implement managed queueing and ECN at the head-end device, eg. DSLAM or cell-tower, and preferably at other vulnerable points in their network too.
Well, if they have a Cisco network, that might work. Few other
network gear vendors actively support ECN.
> 2) Implement TCP *receive* window management. This prevents the TCP algorithm on the sending side from attempting to find the size of the queues in the network. Search the list archives for "Blackpool" to see my take on this technique in the form of a kernel patch. More sophisticated algorithms are doubtless possible.
Probably not something I want to use in production.
Thanks, Johnathan. Now yet another question:
Two different server configurations (these are real life examples, by the way):
1. eth0 and eth1 bound as bond0 with vlans hanging off of them.
Where to put the qdisc? On the bond interface? On the Ethernet
interfaces? On the vlan interfaces?
2. eth0 and eth1 have vlan interfaces attached as eth0.10, eth1.10
and eth0.20, eth1.20. Those are bound to bond interfaces, bond10 and
bond20. Same question, where best to apply the qdisc.
George
next prev parent reply other threads:[~2012-02-05 1:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 0:40 [Bloat] " Dave Taht
2012-01-02 5:22 ` Eric Dumazet
2012-01-02 8:07 ` Dave Taht
2012-01-02 21:31 ` Dave Taht
2012-01-02 22:14 ` Albert Rafetseder
2012-01-02 22:33 ` Dave Taht
2012-01-04 15:25 ` [Bloat] What is fairness, anyway? was: " Jim Gettys
2012-01-04 16:16 ` Dave Taht
2012-01-04 17:23 ` Jim Gettys
2012-01-04 17:36 ` Justin McCann
2012-01-04 17:40 ` Eric Dumazet
[not found] ` <CAFkTFa89mOmbcOV1PWX3my04rK4NsEvyakcQV2j54qa0gzAViQ@mail.g mail.com>
2012-01-05 17:52 ` Bob Briscoe
2012-01-06 17:42 ` Jim Gettys
2012-01-06 18:09 ` Dave Taht
2012-01-06 19:57 ` Eric Dumazet
2012-01-06 20:34 ` Jonathan Morton
2012-01-07 19:42 ` Bob Briscoe
2012-01-07 22:16 ` Wesley Eddy
2012-01-08 0:40 ` Dave Taht
[not found] ` <CAA93jw7xKwdUeT7wFNoiM8RQp1--==Eazdo0ucc44vz+L1U06g@mail.g mail.com>
2012-01-09 5:38 ` Bob Briscoe
2012-01-11 7:26 ` Dave Taht
[not found] ` <CAA93jw4KJdYwrAuk7-yHDYCGBh1s6mE47eAYu2_LRfY45-qZ2g@mail.g mail.com>
2012-01-14 11:06 ` Bob Briscoe
2012-01-13 21:45 ` Dan Siemon
2012-01-14 15:55 ` Dave Taht
2012-01-04 16:22 ` Eric Dumazet
2012-02-05 0:24 ` George B.
2012-02-05 0:43 ` Jonathan Morton
2012-02-05 1:57 ` George B. [this message]
2012-02-05 2:05 ` john thompson
2012-02-05 7:39 ` Eric Dumazet
[not found] ` <CAA93jw68yntHkhETQ1a9-Azu7UXEuU9f5fgOsB25hvA240iApg@mail.gmail.com>
2012-02-05 14:24 ` Dave Taht
2012-02-05 17:53 ` Justin McCann
2012-02-05 18:21 ` Eric Dumazet
2012-01-14 16:35 Jesper Dangaard Brouer
2012-01-15 9:49 ` Dave Taht
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='CAJ2iOjSmEG84DTKTurh_fKVWEmdKuUDL8jN=YKYhyEvMCXWFKg@mail.gmail.com' \
--to=georgeb@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.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