* [PATCH net-next] Documentation: net/smc: correct old value of smcr_max_recv_wr
@ 2026-04-22 8:51 Mahanta Jambigi
2026-04-22 12:08 ` Alexandra Winter
0 siblings, 1 reply; 2+ messages in thread
From: Mahanta Jambigi @ 2026-04-22 8:51 UTC (permalink / raw)
To: andrew+netdev, davem, edumazet, kuba, pabeni, alibuda, dust.li,
sidraya, wenjia
Cc: pasic, horms, tonylu, guwen, netdev, linux-s390, Mahanta Jambigi
The smc-sysctl.rst documentation incorrectly stated that the previous
hardcoded maximum number of WR buffers on the receive path (smcr_max_recv_wr)
was 16. The correct historical value used before the introduction of the sysctl
control was 48. Update the documentation to reflect the accurate default value.
Fixes: aef3cdb47bbb net/smc: make wr buffer count configurable
Reviewed-by: Halil Pasic <pasic@linux.ibm.com>
Reviewed-by: Sidraya Jayagond <sidraya@linux.ibm.com>
Signed-off-by: Mahanta Jambigi <mjambigi@linux.ibm.com>
---
Documentation/networking/smc-sysctl.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/networking/smc-sysctl.rst b/Documentation/networking/smc-sysctl.rst
index 904a910f198e..279d15e61899 100644
--- a/Documentation/networking/smc-sysctl.rst
+++ b/Documentation/networking/smc-sysctl.rst
@@ -100,14 +100,14 @@ smcr_max_recv_wr - INTEGER
depending on the workload it can be a bottleneck in a sense that threads
have to wait for work request buffers to become available. Before the
introduction of this control the maximal number of work request buffers
- available on the receive path used to be hard coded to 16. With this control
+ available on the receive path used to be hard coded to 48. With this control
it becomes configurable. The acceptable range is between 2 and 2048.
Please be aware that all the buffers need to be allocated as a physically
continuous array in which each element is a single buffer and has the size
of SMC_WR_BUF_SIZE (48) bytes. If the allocation fails, we keep retrying
with half of the buffer count until it is ether successful or (unlikely)
- we dip below the old hard coded value which is 16 where we give up much
+ we dip below the old hard coded value which is 48 where we give up much
like before having this control.
Default: 48
--
2.51.0
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH net-next] Documentation: net/smc: correct old value of smcr_max_recv_wr
2026-04-22 8:51 [PATCH net-next] Documentation: net/smc: correct old value of smcr_max_recv_wr Mahanta Jambigi
@ 2026-04-22 12:08 ` Alexandra Winter
0 siblings, 0 replies; 2+ messages in thread
From: Alexandra Winter @ 2026-04-22 12:08 UTC (permalink / raw)
To: Mahanta Jambigi, andrew+netdev, davem, edumazet, kuba, pabeni,
alibuda, dust.li, sidraya, wenjia
Cc: pasic, horms, tonylu, guwen, netdev, linux-s390
net-next is closed!
On 22.04.26 10:51, Mahanta Jambigi wrote:
> The smc-sysctl.rst documentation incorrectly stated that the previous
> hardcoded maximum number of WR buffers on the receive path (smcr_max_recv_wr)
> was 16. The correct historical value used before the introduction of the sysctl
> control was 48. Update the documentation to reflect the accurate default value.
s/default/historical/
or remove the last sentence
>
> Fixes: aef3cdb47bbb net/smc: make wr buffer count configurable
> Reviewed-by: Halil Pasic <pasic@linux.ibm.com>
> Reviewed-by: Sidraya Jayagond <sidraya@linux.ibm.com>
> Signed-off-by: Mahanta Jambigi <mjambigi@linux.ibm.com>
> ---
> Documentation/networking/smc-sysctl.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/networking/smc-sysctl.rst b/Documentation/networking/smc-sysctl.rst
> index 904a910f198e..279d15e61899 100644
> --- a/Documentation/networking/smc-sysctl.rst
> +++ b/Documentation/networking/smc-sysctl.rst
> @@ -100,14 +100,14 @@ smcr_max_recv_wr - INTEGER
> depending on the workload it can be a bottleneck in a sense that threads
> have to wait for work request buffers to become available. Before the
> introduction of this control the maximal number of work request buffers
> - available on the receive path used to be hard coded to 16. With this control
> + available on the receive path used to be hard coded to 48. With this control
> it becomes configurable. The acceptable range is between 2 and 2048.
>
> Please be aware that all the buffers need to be allocated as a physically
> continuous array in which each element is a single buffer and has the size
> of SMC_WR_BUF_SIZE (48) bytes. If the allocation fails, we keep retrying
> with half of the buffer count until it is ether successful or (unlikely)
typo in old documentation: s/ether/either/g
> - we dip below the old hard coded value which is 16 where we give up much
> + we dip below the old hard coded value which is 48 where we give up much
> like before having this control.
>
> Default: 48
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-04-22 12:08 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-04-22 8:51 [PATCH net-next] Documentation: net/smc: correct old value of smcr_max_recv_wr Mahanta Jambigi
2026-04-22 12:08 ` Alexandra Winter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox