[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0f70d4ff-ad35-42ee-8b99-cf6e3da7c49e@linux.ibm.com>
Date: Tue, 28 Oct 2025 15:03:30 +0530
From: Mahanta Jambigi <mjambigi@...ux.ibm.com>
To: Halil Pasic <pasic@...ux.ibm.com>,
"David S. Miller"
<davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
Jonathan Corbet <corbet@....net>,
"D. Wythe" <alibuda@...ux.alibaba.com>,
Dust Li <dust.li@...ux.alibaba.com>,
Sidraya Jayagond <sidraya@...ux.ibm.com>,
Wenjia Zhang
<wenjia@...ux.ibm.com>,
Tony Lu <tonylu@...ux.alibaba.com>, netdev@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-rdma@...r.kernel.org, linux-s390@...r.kernel.org
Cc: Wen Gu <guwen@...ux.alibaba.com>,
Guangguan Wang <guangguan.wang@...ux.alibaba.com>,
Bagas Sanjaya <bagasdotme@...il.com>
Subject: Re: [PATCH net-next v6 1/2] net/smc: make wr buffer count
configurable
On 28/10/25 4:18 am, Halil Pasic wrote:
> Think SMC_WR_BUF_CNT_SEND := SMC_WR_BUF_CNT used in send context and
> SMC_WR_BUF_CNT_RECV := 3 * SMC_WR_BUF_CNT used in recv context. Those
> get replaced with lgr->max_send_wr and lgr->max_recv_wr respective.
>
> Please note that although with the default sysctl values
> qp_attr.cap.max_send_wr == qp_attr.cap.max_recv_wr is maintained but
> can not be assumed to be generally true any more. I see no downside to
> that, but my confidence level is rather modest.
>
> Signed-off-by: Halil Pasic <pasic@...ux.ibm.com>
> Reviewed-by: Sidraya Jayagond <sidraya@...ux.ibm.com>
> Reviewed-by: Dust Li <dust.li@...ux.alibaba.com>
> ---
Tested-by: Mahanta Jambigi <mjambigi@...ux.ibm.com>
Powered by blists - more mailing lists