From: Sahaj Chaudhari <sahaj123.sc@gmail.com>
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, shuah@kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/net: test tcp_rmem lower bound
Date: Mon, 12 Oct 2026 16:56:34 +0530 [thread overview]
Message-ID: <20261012112634.3371756-1-sahaj123.sc@gmail.com> (raw)
In-Reply-To: <9b4b59ac-6e64-4dd2-88c1-c3f7844bbd36@kernel.org>
Hi Eric,
Thanks for the review. I agree that a separate test for each sysctl bound
does not scale and that this focused tcp_rmem test is not the right fit. I
won't send a v2 of it.
Your points about the non-portable 4096 assumption and partial updates are
also noted. The generic network-sysctl test you described is broader work;
I'll treat it separately rather than expanding this patch.
Thanks,
Sahaj
prev parent reply other threads:[~2026-10-12 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 5:45 [PATCH] selftests/net: test tcp_rmem lower bound Sahaj Chaudhari
2026-10-07 6:14 ` Eric Dumazet
2026-10-12 11:26 ` Sahaj Chaudhari [this message]
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=20261012112634.3371756-1-sahaj123.sc@gmail.com \
--to=sahaj123.sc@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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