From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, ncardwell@google.com, ycheng@google.com,
maze@google.com
Subject: Re: [PATCH] tcp: sndbuf autotuning improvements
Date: Wed, 02 Oct 2013 16:46:00 -0400 (EDT) [thread overview]
Message-ID: <20131002.164600.347083935801850982.davem@davemloft.net> (raw)
In-Reply-To: <1380648224.19002.32.camel@edumazet-glaptop.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 01 Oct 2013 10:23:44 -0700
> From: Eric Dumazet <edumazet@google.com>
>
> tcp_fixup_sndbuf() is underestimating initial send buffer requirements.
>
> It was not noticed because big GSO packets were escaping the limitation,
> but with smaller TSO packets (or TSO/GSO/SG off), application hits
> sk_sndbuf before having a chance to fill enough packets in socket write
> queue.
>
> - initial cwnd can be bigger than 10 for specific routes
>
> - SKB_TRUESIZE() is a bit under real needs in some cases,
> because of power-of-two rounding in kmalloc()
>
> - Fast Recovery (RFC 5681 3.2) : Cubic needs 70% factor
>
> - Extra cushion (application might react slowly to POLLOUT)
>
> tcp_v4_conn_req_fastopen() needs to call tcp_init_metrics() before
> calling tcp_init_buffer_space()
>
> Then we realize tcp_new_space() should call tcp_fixup_sndbuf()
> instead of duplicating this stuff.
>
> Rename tcp_fixup_sndbuf() to tcp_sndbuf_expand() to be more
> descriptive.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Signed-off-by: Neal Cardwell <ncardwell@google.com>
> Signed-off-by: Yuchung Cheng <ycheng@google.com>
> Acked-by: Maciej Żenczykowski <maze@google.com>
I assume this is meant for net-next as that is where this applies
cleanly.
Applied, thanks.
next prev parent reply other threads:[~2013-10-02 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 17:23 [PATCH] tcp: sndbuf autotuning improvements Eric Dumazet
2013-10-02 20:46 ` David Miller [this message]
2013-10-02 21:07 ` Eric Dumazet
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=20131002.164600.347083935801850982.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=maze@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--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