From: Jonathan Corbet <corbet@lwn.net>
To: Shubham Chakraborty <chakrabortyshubham66@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
Subject: Re: [PATCH] Documentation: sysctl: document net core sysctls
Date: Thu, 09 Apr 2026 08:19:17 -0600 [thread overview]
Message-ID: <87fr54cj2y.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260407083213.27045-1-chakrabortyshubham66@gmail.com>
Shubham Chakraborty <chakrabortyshubham66@gmail.com> writes:
Thanks for working to make our documentation better. A few notes,
though...
This is a networking-related patch, so it really needs to go to the
networking maintainers.
> Document missing net.core and net.unix sysctl entries in admin-guide/sysctl/net.rst, and correct wording for defaults that are derived from PAGE_SIZE, HZ, or CONFIG_MAX_SKB_FRAGS.
>
> Also clarify that the RFS and flow-limit controls are only present when CONFIG_RPS or CONFIG_NET_FLOW_LIMIT is enabled, and describe rps_sock_flow_entries the way the handler implements it: non-zero values are rounded up to the nearest power of two.
Please word-wrap your changelog text.
> Validation: git diff --check -- Documentation/admin-guide/sysctl/net.rst
> Validation: make -j1 O=/tmp/linux-docs-check SPHINXDIRS=admin-guide/sysctl htmldocs
This isn't a recognized tag, so shouldn't be expressed this way. If you
want, you can describe your testing setup after the "---" line.
> Signed-off-by: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
> ---
> Documentation/admin-guide/sysctl/net.rst | 66 +++++++++++++++++++++++-
> 1 file changed, 64 insertions(+), 2 deletions(-)
The actual changes are best reviewed by the networking developers.
Thanks,
jon
next prev parent reply other threads:[~2026-04-09 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 8:32 [PATCH] Documentation: sysctl: document net core sysctls Shubham Chakraborty
2026-04-09 14:19 ` Jonathan Corbet [this message]
2026-04-09 17:48 ` [PATCH v2] " Shubham Chakraborty
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=87fr54cj2y.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=chakrabortyshubham66@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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