From: Rick Jones <rick.jones2@hp.com>
To: Jim Rees <rees@umich.edu>
Cc: netdev@vger.kernel.org
Subject: Re: Autotuning and send buffer size
Date: Fri, 11 Jul 2008 09:48:06 -0700 [thread overview]
Message-ID: <48778EC6.8070507@hp.com> (raw)
In-Reply-To: <20080711150208.GA15305@citi.umich.edu>
> I don't undestand how a "too big" sender buffer can hurt performance. I
> have not measured what size the sender's buffer is in the autotuning case.
In broad handwaving terms, TCP will have no more data outstanding at one
time than the lesser of:
*) what the application has sent
*) the current value of the computed congestion window
*) the receiver's advertised window
*) the quantity of data TCP can hold in its retransmission queue
That last one is, IIRC directly related to "SO_SNDBUF"
That leads to an hypothesis of all of those being/growing large enough
to overflow a queue somewhere - for example an interface's transmit
queue and causing retransmissions. Ostensibly, one could check that in
ifconfig and/or netstat statistics.
rick jones
next prev parent reply other threads:[~2008-07-11 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 15:02 Autotuning and send buffer size Jim Rees
2008-07-11 16:48 ` Rick Jones [this message]
2008-07-11 21:01 ` Bill Fink
2008-07-11 17:07 ` Bill Fink
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=48778EC6.8070507@hp.com \
--to=rick.jones2@hp.com \
--cc=netdev@vger.kernel.org \
--cc=rees@umich.edu \
/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).