From: Stephen Hemminger <stephen@networkplumber.org>
To: Ivan Babrou <ivan@cloudflare.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@cloudflare.com,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net] tcp: note that tcp_rmem[1] has a limited range
Date: Mon, 3 Jan 2022 16:44:43 -0800 [thread overview]
Message-ID: <20220103164443.53b7b8d5@hermes.local> (raw)
In-Reply-To: <20220104003722.73982-1-ivan@cloudflare.com>
On Mon, 3 Jan 2022 16:37:22 -0800
Ivan Babrou <ivan@cloudflare.com> wrote:
> The value of rcv_ssthresh is limited to tcp_rwin, which is limited
> to 64k at the handshake time, since window scaling is not allowed there.
>
> Let's add a note to the docs that increasing tcp_rmem[1] does not have
> any effect on raising the initial value of rcv_ssthresh past 64k.
>
> Link: https://lkml.org/lkml/2021/12/22/652
> Signed-off-by: Ivan Babrou <ivan@cloudflare.com>
> ---
> Documentation/networking/ip-sysctl.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/networking/ip-sysctl.rst b/Documentation/networking/ip-sysctl.rst
> index 2572eecc3e86..16528bc92e65 100644
> --- a/Documentation/networking/ip-sysctl.rst
> +++ b/Documentation/networking/ip-sysctl.rst
> @@ -683,7 +683,8 @@ tcp_rmem - vector of 3 INTEGERs: min, default, max
> default: initial size of receive buffer used by TCP sockets.
> This value overrides net.core.rmem_default used by other protocols.
> Default: 131072 bytes.
> - This value results in initial window of 65535.
> + This value results in initial window of 65535. Increasing this value
> + won't raise the initial advertised window above 65535.
>
> max: maximal size of receive buffer allowed for automatically
> selected receiver buffers for TCP socket. This value does not override
Why not add error check or warning in write to sysctl?
next prev parent reply other threads:[~2022-01-04 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 0:37 [PATCH net] tcp: note that tcp_rmem[1] has a limited range Ivan Babrou
2022-01-04 0:44 ` Stephen Hemminger [this message]
2022-01-04 8:33 ` Eric Dumazet
2022-01-06 4:20 ` Ivan Babrou
2022-01-06 8:25 ` Eric Dumazet
2022-01-06 22:40 ` Ivan Babrou
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=20220103164443.53b7b8d5@hermes.local \
--to=stephen@networkplumber.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ivan@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).