From: Fred Baker <fred@cisco.com>
To: Dave Taht <dave.taht@gmail.com>,
"Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Best practices for paced TCP on Linux?
Date: Sat, 7 Apr 2012 14:49:53 -0700 [thread overview]
Message-ID: <6D19B807-1B09-4AB5-A727-E9A7449C6A1D@cisco.com> (raw)
In-Reply-To: <CAA93jw5hPBmonhuoww9MqB0z0-uncatP5jGMrrCAepH5ouUwrQ@mail.gmail.com>
On Apr 7, 2012, at 11:50 AM, Dave Taht wrote:
> http://www.kernel.org/doc/man-pages/online/pages/man7/tcp.7.html
>
> 64-256k seems about right but the math is eluding me this morning.
For a 5 MBPS data stream, Path MTU = 1460, 100 ms RTT, you're looking at
rate in bps rtt in microseconds
cwnd_limit = ceiling ( ----------- * ------------------- )
8*pmtu 1e6
5e6 100 e 3
= ceiling ( ------ * ------------------- )
8*1460 1e6
= ceiling ( 428 * 0.100 )
= 43
you probably want to bump that by one or two to account for 43*40 bytes of IP and TCP headers.
43*1460 is 62780 bytes per RTT, which is frightfully close to 65K bytes per RTT, 524,280 bits per RTT, or 5,242,800 bits per second with the stated RTT. Hmmm.
Speaking strictly for myself, I would throw in one caveat, which is that a variable bit rate codec that averages 5 MBPS sometimes sends faster, and there may be good reason to allow it to. I think I'd recalculate for 6 MBPS on average, and carefully insert the RTT I cared about into the calculation. Doing that also accounts for the Mathis formula, which is far more complex and requires a lot more assumptions, but will come up with a number below 6 MBPS for a .1% loss rate.
next prev parent reply other threads:[~2012-04-07 21:51 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
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 [this message]
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=6D19B807-1B09-4AB5-A727-E9A7449C6A1D@cisco.com \
--to=fred@cisco.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--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