From: "Schumaker, Anna" <Anna.Schumaker@netapp.com>
To: "bfields@fieldses.org" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"thomas.preston@codethink.co.uk" <thomas.preston@codethink.co.uk>,
"jlayton@kernel.org" <jlayton@kernel.org>
Cc: "linux-kernel@lists.codethink.co.uk"
<linux-kernel@lists.codethink.co.uk>,
"ben.dooks@codethink.co.uk" <ben.dooks@codethink.co.uk>
Subject: Re: [PATCH v2 1/1] SUNRPC: allow /proc entries without CONFIG_SUNRPC_DEBUG
Date: Wed, 28 Nov 2018 21:38:28 +0000 [thread overview]
Message-ID: <dbacc0e7939c409057482e0ccc0f623b15f7ecb8.camel@netapp.com> (raw)
In-Reply-To: <20181128150558.9455-2-thomas.preston@codethink.co.uk>
Hi Thomas,
On Wed, 2018-11-28 at 15:05 +0000, Thomas Preston wrote:
> From: Ben Dooks <ben.dooks@codethink.co.uk>
>
> If we want /proc/sys/sunrpc the current kernel also drags in other debug
> features which we don't really want. Instead, we should always show the
> following entries:
>
> /proc/sys/sunrpc/udp_slot_table_entries
> /proc/sys/sunrpc/tcp_slot_table_entries
> /proc/sys/sunrpc/tcp_max_slot_table_entries
> /proc/sys/sunrpc/min_resvport
> /proc/sys/sunrpc/max_resvport
> /proc/sys/sunrpc/tcp_fin_timeout
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> Signed-off-by: Thomas Preston <thomas.preston@codethink.co.uk>
Thanks, this looks great to me!
Anna
> ---
> net/sunrpc/xprtsock.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/net/sunrpc/xprtsock.c b/net/sunrpc/xprtsock.c
> index ae77c71c1f64..c6c07fa410d1 100644
> --- a/net/sunrpc/xprtsock.c
> +++ b/net/sunrpc/xprtsock.c
> @@ -68,8 +68,6 @@ static unsigned int xprt_max_tcp_slot_table_entries =
> RPC_MAX_SLOT_TABLE;
> static unsigned int xprt_min_resvport = RPC_DEF_MIN_RESVPORT;
> static unsigned int xprt_max_resvport = RPC_DEF_MAX_RESVPORT;
>
> -#if IS_ENABLED(CONFIG_SUNRPC_DEBUG)
> -
> #define XS_TCP_LINGER_TO (15U * HZ)
> static unsigned int xs_tcp_fin_timeout __read_mostly = XS_TCP_LINGER_TO;
>
> @@ -159,8 +157,6 @@ static struct ctl_table sunrpc_table[] = {
> { },
> };
>
> -#endif
> -
> /*
> * Wait duration for a reply from the RPC portmapper.
> */
> @@ -3114,10 +3110,8 @@ static struct xprt_class xs_bc_tcp_transport = {
> */
> int init_socket_xprt(void)
> {
> -#if IS_ENABLED(CONFIG_SUNRPC_DEBUG)
> if (!sunrpc_table_header)
> sunrpc_table_header = register_sysctl_table(sunrpc_table);
> -#endif
>
> xprt_register_transport(&xs_local_transport);
> xprt_register_transport(&xs_udp_transport);
> @@ -3133,12 +3127,10 @@ int init_socket_xprt(void)
> */
> void cleanup_socket_xprt(void)
> {
> -#if IS_ENABLED(CONFIG_SUNRPC_DEBUG)
> if (sunrpc_table_header) {
> unregister_sysctl_table(sunrpc_table_header);
> sunrpc_table_header = NULL;
> }
> -#endif
>
> xprt_unregister_transport(&xs_local_transport);
> xprt_unregister_transport(&xs_udp_transport);
prev parent reply other threads:[~2018-11-28 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 15:05 [PATCH v2 0/1] SUNRPC: Allow /proc entries without CONFIG_SUNRPC_DEBUG Thomas Preston
2018-11-28 15:05 ` [PATCH v2 1/1] SUNRPC: allow " Thomas Preston
2018-11-28 21:38 ` Schumaker, Anna [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=dbacc0e7939c409057482e0ccc0f623b15f7ecb8.camel@netapp.com \
--to=anna.schumaker@netapp.com \
--cc=ben.dooks@codethink.co.uk \
--cc=bfields@fieldses.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-nfs@vger.kernel.org \
--cc=thomas.preston@codethink.co.uk \
/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