From: Dave Taht <dave.taht@gmail.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Best practices for paced TCP on Linux?
Date: Sat, 7 Apr 2012 08:52:50 -0700 [thread overview]
Message-ID: <CAA93jw7MF5UZNeRrt9TT2YpCr1gJhoyeZx8yCm39MXHfcs=G1Q@mail.gmail.com> (raw)
In-Reply-To: <20120407153548.GC21452@uio.no>
On Sat, Apr 7, 2012 at 8:35 AM, Steinar H. Gunderson
<sgunderson@bigfoot.com> wrote:
> On Sat, Apr 07, 2012 at 08:25:18AM -0700, Dave Taht wrote:
>> The test HD tcp stream is up at
>>
>> http://cesur.tg12.gathering.org:9094/
>
> That's the SD stream. http://stream.tg12.gathering.org/ has HD etc.
>
>> I'd like to look into what percentage of the failures I observed
>> happened on the wifi hop vs the ethernet gateway
>> since then many changes where made, and I'm low on sleep. (what do
>> geeks do on a friday night?)
>
> FWIW, most of the users complaining don't have wifi in the mix at all.
>
>> I don't know if they are still trying sfqred or qfq in production -
>> they worked! - but had little effect (as is to be kind of expected
>> with the instantaneous queue length being so short and bandwidth so
>> high on their first and nearest hops....)
>
> The one on cesur.tg12 has sfqred + my hacked VLC to do TCP pacing.
kernel 3.3?
please send:
tc -s qdisc show dev the_device
cd /sys/class/net/the_device/queues/tx-0/byte_queue_limits
cat inflight
cat limit
> The one on stream.tg12 has the oddest “shaping” in a while; the 10GigE is
> terminated in a Cisco 4948E which then has a 8x1GigE trunk out. We hope this
> will smooth out the worst bursts a bit.
>
> /* Steinar */
> --
> Homepage: http://www.sesse.net/
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
next prev parent reply other threads:[~2012-04-07 15:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 21:37 Steinar H. Gunderson
2012-04-06 21:49 ` Dave Taht
2012-04-06 22:21 ` Steinar H. Gunderson
2012-04-07 15:08 ` Eric Dumazet
2012-04-07 15:25 ` Dave Taht
2012-04-07 15:35 ` Steinar H. Gunderson
2012-04-07 15:48 ` Dave Taht
2012-04-07 15:52 ` Dave Taht [this message]
2012-04-07 17:10 ` Jonathan Morton
2012-04-07 17:18 ` Dave Taht
2012-04-07 17:44 ` Jonathan Morton
2012-04-07 18:10 ` Steinar H. Gunderson
2012-04-07 18:27 ` Jonathan Morton
2012-04-07 18:56 ` Dave Taht
2012-04-07 18:50 ` Dave Taht
2012-04-07 18:54 ` Steinar H. Gunderson
2012-04-07 19:01 ` Steinar H. Gunderson
2012-04-07 19:08 ` Jonathan Morton
2012-04-07 19:38 ` Dave Taht
2012-04-07 20:16 ` Steinar H. Gunderson
2012-04-14 0:37 ` Rick Jones
2012-04-07 21:13 ` Jesper Dangaard Brouer
2012-04-07 21:31 ` Steinar H. Gunderson
2012-04-07 19:02 ` Dave Taht
2012-04-07 21:49 ` Fred Baker
2012-04-07 22:36 ` Dave Taht
2012-04-07 23:59 ` Fred Baker
2012-04-07 20:27 ` Neil Davies
2012-04-14 0:35 ` Rick Jones
2012-04-14 21:06 ` Roger Jørgensen
2012-04-16 17:05 ` Rick Jones
2012-04-07 11:54 ` Neil Davies
2012-04-07 14:17 ` Fred Baker
2012-04-07 15:08 ` Neil Davies
2012-04-07 15:16 ` Steinar H. Gunderson
2012-04-14 0:44 ` Rick Jones
2012-04-07 14:48 ` Dave Taht
2012-05-12 20:08 ` Steinar H. Gunderson
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='CAA93jw7MF5UZNeRrt9TT2YpCr1gJhoyeZx8yCm39MXHfcs=G1Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=sgunderson@bigfoot.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