public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "D. Wythe" <alibuda@linux.alibaba.com    >
To: sawara04.o@gmail.com
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, corbet@lwn.net,
	skhan@linuxfoundation.org, netdev@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net/smc: Add documentation for limit_smc_hs and hs_ctrl
Date: Thu, 5 Mar 2026 19:24:28 +0800	[thread overview]
Message-ID: <20260305112428.GA57792@j66a10360.sqa.eu95> (raw)
In-Reply-To: <20260305092226.27379-3-sawara04.o@gmail.com>

On Thu, Mar 05, 2026 at 06:22:24PM +0900, sawara04.o@gmail.com wrote:
> From: Kyoji Ogasawara <sawara04.o@gmail.com>
> 
> Document missing SMC sysctl parameters limit_smc_hs and hs_ctrl
> 
> Signed-off-by: Kyoji Ogasawara <sawara04.o@gmail.com>
> ---
>  Documentation/networking/smc-sysctl.rst | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> diff --git a/Documentation/networking/smc-sysctl.rst b/Documentation/networking/smc-sysctl.rst
> index 17b8314c0e5e..67c2bdc533d7 100644
> --- a/Documentation/networking/smc-sysctl.rst
> +++ b/Documentation/networking/smc-sysctl.rst
> @@ -111,3 +111,27 @@ smcr_max_recv_wr - INTEGER
>  	like before having this control.
>  
>  	Default: 48
> +
> +limit_smc_hs - INTEGER
> +	Whether to limit SMC handshake for newly created sockets.
> +
> +	When enabled, SMC listen path applies handshake limitation based on
> +	handshake worker congestion and queued SMC handshake load.
> +
> +	Possible values:
> +
> +	- 0 - Disable handshake limitation
> +	- 1 - Enable handshake limitation
> +
> +	Default: 0 (disable)
> +
> +hs_ctrl - STRING
> +	Select the SMC handshake control profile by name.
> +
> +	The selected profile controls whether SMC options are advertised
> +	during TCP SYN/SYN-ACK handshake.
> +
> +	Only available when CONFIG_SMC_HS_CTRL_BPF is enabled.
> +	Write an empty string to clear the current profile.

It would be better to clarify that this string refers to the name of a
BPF struct_ops (type smc_hs_ctrl) implemented by the user.

> +
> +	Default: empty string
> \ No newline at end of file
> -- 
> 2.43.0
> 

  reply	other threads:[~2026-03-05 11:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05  9:22 [PATCH net-next 0/2] smc-sysctl formatting and missing entries sawara04.o
2026-03-05  9:22 ` [PATCH net-next 1/2] net/smc: fix indentation in smcr_buf_type section sawara04.o
2026-03-05  9:22 ` [PATCH net-next 2/2] net/smc: Add documentation for limit_smc_hs and hs_ctrl sawara04.o
2026-03-05 11:24   ` D. Wythe [this message]
2026-03-05 16:40     ` Kyoji Ogasawara
2026-03-06  2:28       ` D. Wythe

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=20260305112428.GA57792@j66a10360.sqa.eu95 \
    --to=alibuda@linux.alibaba.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sawara04.o@gmail.com \
    --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