From: Zach Brown <zach.brown@oracle.com>
To: netdev@vger.kernel.org
Subject: tune back idle cwnd closing?
Date: Fri, 21 Apr 2006 12:58:56 -0700 [thread overview]
Message-ID: <44493980.1040708@oracle.com> (raw)
My apologies if this is a FAQ, I couldn't find it in the archives.
We have some dudes who are syncing large amounts of data across a
dedicated long fat pipe at somewhat irregular intervals that are, sadly,
longer than the rto. They feel the pain of having to reopen the window
between transmissions.
Is there room for a compromise tunable that would be less aggressive
about closing cwnd during idle periods but which wouldn't violate the
spirit of 2861? No one wants broken TCP here.
They mention that Solaris has the tcp_slow_start_after_idle tunable and
that it helps their situation. I mention that only as a data point, I
wouldn't be foolish enough to try and use the presence of something in
Solaris as justification :)
- z
next reply other threads:[~2006-04-21 19:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 19:58 Zach Brown [this message]
2006-04-25 14:27 ` tune back idle cwnd closing? John Heffner
2006-04-26 21:45 ` David S. Miller
2006-04-26 22:16 ` Rick Jones
2006-04-26 22:27 ` Stephen Hemminger
2006-04-26 22:44 ` Rick Jones
2006-04-26 22:33 ` David S. Miller
2006-04-26 23:25 ` Zach Brown
2006-04-27 17:47 ` John Heffner
2006-04-27 20:19 ` David S. Miller
2006-04-27 21:12 ` Rick Jones
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=44493980.1040708@oracle.com \
--to=zach.brown@oracle.com \
--cc=netdev@vger.kernel.org \
/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).