All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
	Neal Cardwell <ncardwell@google.com>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 2/2] tcp: add net.ipv4.tcp_rtt_threshold sysctl
Date: Wed, 19 Nov 2025 09:59:45 +0100	[thread overview]
Message-ID: <9e1011a8-70bd-468d-96b2-a306039b97f9@redhat.com> (raw)
In-Reply-To: <CANn89iLGXY0qhvNNZWVppq+u0kccD5QCVAEqZ_0GyZGGeWL=Yg@mail.gmail.com>

On 11/18/25 10:22 PM, Eric Dumazet wrote:
> I would perhaps use 8 senders, and force all receivers on one cpu (cpu
> 4 in the following run)
> 
> for i in {1..8}
> do
>  netperf -H host -T,4 -l 100 &
> done
> 
> This would I think show what can happen when receivers can not keep up.

Thanks for the suggestion. I should have understood the receiver needs
to be under stress in the relevant scenario.

With the above setup, on vanilla kernel, the rcvbuf I see is:

min 2134391 max 33554432 avg 12085941

with multiple connections hitting tcp_rmem[2]

with the patched kernel:

min 1192472 max 33554432 avg 4247351

there is a single outlier hitting tcp_rmem[2], and in that case the
connection observes for some samples a rtt just above tcp_rtt_threshold
sysctl/tcp_rcvbuf_low_rtt.

FWIW I guess you can add:

Tested-by: Paolo Abeni <pabeni@redhat.com>

Thanks,

Paolo


  parent reply	other threads:[~2025-11-19  8:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 13:28 [PATCH net-next 0/2] tcp: tcp_rcvbuf_grow() changes Eric Dumazet
2025-11-17 13:28 ` [PATCH net-next 1/2] tcp: tcp_moderate_rcvbuf is only used in rx path Eric Dumazet
2025-11-18  4:13   ` Kuniyuki Iwashima
2025-11-17 13:28 ` [PATCH net-next 2/2] tcp: add net.ipv4.tcp_rtt_threshold sysctl Eric Dumazet
2025-11-18  4:39   ` Kuniyuki Iwashima
2025-11-18 14:04   ` Neal Cardwell
2025-11-18 16:10     ` Eric Dumazet
2025-11-18 21:14   ` Paolo Abeni
2025-11-18 21:22     ` Eric Dumazet
2025-11-19  8:01       ` Eric Dumazet
2025-11-19  8:59       ` Paolo Abeni [this message]
2025-11-19  9: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=9e1011a8-70bd-468d-96b2-a306039b97f9@redhat.com \
    --to=pabeni@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=ncardwell@google.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.