Netdev List
 help / color / mirror / Atom feed
From: Sahaj Chaudhari <sahaj123.sc@gmail.com>
To: Hangbin Liu <hangbin.liu@linux.dev>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] selftests/net: test network sysctl extremes
Date: Sun, 25 Oct 2026 21:39:27 +0530	[thread overview]
Message-ID: <20261025160927.3934600-2-sahaj123.sc@gmail.com> (raw)
In-Reply-To: <atXJLy6iTh5vbe9D@fedora>

Hi Hangbin,

Thanks for asking. C was a choice, not a requirement; I agree shell is
clearer for simple sysctl toggles. This test also searches accepted bounds
for each value in a sysctl vector, verifies writes, restores the original
vector, exercises loopback, and checks kernel log records. I chose C to
make the numeric and error handling explicit. My shell prototype was
unreliable in QEMU when parsing the vectors and reading /dev/kmsg; I don't
mean that shell could not be made to handle those cases.

I've narrowed the test to tcp_rmem and tcp_wmem; UDP is now only a
transport smoke check. I recognize the C implementation is sizeable, so
if you think that complexity isn't warranted for this coverage, I'm open
to simplifying or folding the test into an existing one.

Thanks,
Sahaj

      reply	other threads:[~2026-10-25 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  4:14 [PATCH net v2] selftests/net: test network sysctl extremes Sahaj Chaudhari
2026-10-18  4:35 ` netdev-bot+sashiko
2026-10-19  7:39 ` Hangbin Liu
2026-10-25 16:09   ` 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=20261025160927.3934600-2-sahaj123.sc@gmail.com \
    --to=sahaj123.sc@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=hangbin.liu@linux.dev \
    --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