From: Eric Dumazet <eric.dumazet@gmail.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Yuchung Cheng <ycheng@google.com>,
Neal Cardwell <ncardwell@google.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH v3 net-next 2/2] tcp: TCP_NOTSENT_LOWAT socket option
Date: Tue, 23 Jul 2013 10:18:02 -0700 [thread overview]
Message-ID: <1374599882.3449.46.camel@edumazet-glaptop> (raw)
In-Reply-To: <51EEAD54.2040603@hp.com>
On Tue, 2013-07-23 at 09:20 -0700, Rick Jones wrote:
> Isn't this change really just trying to paper-over the autotuning's
> over-growing of the socket buffers? Or are you considering it an
> extension of the auto-tuning heuristics?
>
> If your 20Gbit test setup needed only 256KB socket buffers (figure
> pulled form the ether) to get to 17 Gbit/s, isn't the autotuning's
> growing them to several MB a bug in the autotuning?
As long as we limit the number of unsent bytes, there is no longer an
over provisioning problem.
TCP stack will be able to use the large windows if _needed_ by current
network conditions, receiver (in)ability to drain the data, and if
allowed by congestion control constraints.
If now you are complaining that TCP congestion controls are bad, thats a
completely different story, and this patch does not claim to solve this.
next prev parent reply other threads:[~2013-07-23 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 3:27 [PATCH v3 net-next 2/2] tcp: TCP_NOTSENT_LOWAT socket option Eric Dumazet
2013-07-23 3:52 ` Hannes Frederic Sowa
2013-07-23 15:26 ` Rick Jones
2013-07-23 15:44 ` Eric Dumazet
2013-07-23 16:20 ` Rick Jones
2013-07-23 16:48 ` Eric Dumazet
2013-07-23 17:18 ` Eric Dumazet [this message]
2013-07-23 18:24 ` Yuchung Cheng
2013-07-25 0:55 ` David Miller
2013-07-23 19:19 Neal Cardwell
2013-07-23 19:28 Neal Cardwell
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=1374599882.3449.46.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=mtk.manpages@gmail.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=ycheng@google.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;
as well as URLs for NNTP newsgroup(s).