From: "D. Wythe" <alibuda@linux.alibaba.com >
To: Kyoji Ogasawara <sawara04.o@gmail.com>
Cc: "D. Wythe" <alibuda@linux.alibaba.com>,
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: Fri, 6 Mar 2026 10:28:42 +0800 [thread overview]
Message-ID: <20260306022842.GA85615@j66a10360.sqa.eu95> (raw)
In-Reply-To: <CAKNDObDc55sL1fuQGfEiw13GwzG4WuNm5_ZfAf+_gZNVXuGJQw@mail.gmail.com>
On Fri, Mar 06, 2026 at 01:40:39AM +0900, Kyoji Ogasawara wrote:
> > > +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.
> >
>
> Thanks for the suggestion.
> I updated the hs_ctrl description to clarify that the string is the
> name of a user-implemented BPF struct_ops instance of type
> smc_hs_ctrl.
> Does this address your comment?
>
> ```
> hs_ctrl - STRING
> Select the SMC handshake control profile by name.
>
> + This string refers to the name of a user-implemented
> + BPF struct_ops instance of type smc_hs_ctrl.
> +
> 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.
>
> Default: empty string
> ```
LGTM. Thanks for your contribution.
D. Wythe
prev parent reply other threads:[~2026-03-06 2:28 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
2026-03-05 16:40 ` Kyoji Ogasawara
2026-03-06 2:28 ` D. Wythe [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=20260306022842.GA85615@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