From: Jiri Slaby <jirislaby@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Soheil Hassas Yeganeh <soheil@google.com>,
Neal Cardwell <ncardwell@google.com>,
Yuchung Cheng <ycheng@google.com>,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] tcp: get rid of sysctl_tcp_adv_win_scale
Date: Fri, 3 Nov 2023 11:14:56 +0100 [thread overview]
Message-ID: <28e2bd4a-3233-471c-a1ae-57a445173401@kernel.org> (raw)
In-Reply-To: <CANn89iJOwQUwAVcofW+X_8srFcPnaWKyqOoM005L6Zgh8=OvpA@mail.gmail.com>
On 03. 11. 23, 9:17, Eric Dumazet wrote:
> What happens if you double /proc/sys/net/ipv4/tcp_wmem and/or
> /proc/sys/net/ipv4/tcp_rmem first value ?
> (4096 -> 8192)
No change:
# cat /proc/sys/net/ipv4/tcp_wmem
8192 16384 4194304
But this:
# cat /proc/sys/net/ipv4/tcp_rmem
8192 16384 4194304
results in test to run 4.7 s, so even 3 more times slower!
thanks,
--
js
suse labs
next prev parent reply other threads:[~2023-11-03 10:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 15:29 [PATCH net-next] tcp: get rid of sysctl_tcp_adv_win_scale Eric Dumazet
2023-07-17 16:52 ` Soheil Hassas Yeganeh
2023-07-17 17:17 ` Eric Dumazet
2023-07-17 17:20 ` Soheil Hassas Yeganeh
2023-07-19 2:10 ` patchwork-bot+netdevbpf
2023-07-20 15:41 ` Paolo Abeni
2023-07-20 15:50 ` Eric Dumazet
2023-11-03 6:10 ` Jiri Slaby
2023-11-03 6:56 ` Jiri Slaby
2023-11-03 7:07 ` Jiri Slaby
2023-11-03 8:17 ` Eric Dumazet
2023-11-03 9:27 ` Michal Kubecek
2023-11-03 9:53 ` Eric Dumazet
2023-11-03 10:14 ` Jiri Slaby [this message]
2023-11-03 10:27 ` Eric Dumazet
2023-11-03 11:07 ` Jiri Slaby
2024-04-02 15:28 ` shironeko
2024-04-02 15:50 ` Eric Dumazet
2024-04-02 16:23 ` Eric Dumazet
2024-04-02 16:29 ` shironeko
2024-04-06 0:22 ` shironeko
2024-04-06 6:11 ` Eric Dumazet
2024-04-06 7: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=28e2bd4a-3233-471c-a1ae-57a445173401@kernel.org \
--to=jirislaby@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=soheil@google.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