From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] tcp!
Date: Sat, 18 Aug 2012 16:11:13 -0400 [thread overview]
Message-ID: <1835b565a7a0babdf4dc6f2787284674@brasstown.quanstro.net> (raw)
since it came up, i put my working copy of tcp along with some testing
scripts in /n/sources/contrib/quanstro/tcp.
there are a number of fixes rolled into this, but the main fixes are
- add support for new reno,
- properly handle zero-window probes (on both ends),
- don't confuse the cwind with the receiver's advertized window. this
particular condition can lead to livelock.
- don't confuse the window scale with the amount of local buffering
we'd like to do.
- and, don't queue tcp infinitely, which can crash kernels. :-)
i don't have the numbers for the old tcp handy, but i think you'll
be surprised at how much difference there can be. i saw differences
of 20x when the sender was limited in how fast it could read by the
read rate from user space.
i've included "testscript." for the two machines i have handy, i get
the following results with new and old tcp.
machine stack kernel 0ms delay 1ms delay
ideal - 386 unlimited 8.19mb/s
xeon x5550 old 386 138mb/s 0.49mb/s (!)
intel atom old 386 37.2mb/s 0.10mb/s
amd x4 964 new 386 145mb/s 8.03mb/s
intel e31220 new amd64 303mb/s 8.15mb/s
intel atom new 386 67mb/s 8.03mb/s
# note: i can get up to 80mb/s using forsyth's qmalloc.
- erik
next reply other threads:[~2012-08-18 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 20:11 erik quanstrom [this message]
2012-08-18 20:26 ` erik quanstrom
2012-08-19 13:37 ` Richard Miller
2012-08-19 13:55 ` cinap_lenrek
2012-08-19 14:05 ` Richard Miller
2012-08-19 15:07 ` erik quanstrom
2012-08-19 14:48 ` erik quanstrom
2012-08-19 13:17 ` Richard Miller
2012-08-19 15:43 ` erik quanstrom
2012-08-21 18:32 Richard Miller
2012-08-22 17:18 ` Gorka Guardiola
2012-08-22 18:29 ` Steven Stallion
[not found] ` <CAGGHmKFokgrbH1P_j+31teoO9ubEvLu2Ti7_QP1+WPLXQ291Mg@mail.gmail.c>
2012-08-22 18:46 ` erik quanstrom
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1835b565a7a0babdf4dc6f2787284674@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).