From: Paolo Abeni <pabeni@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
"D. Wythe" <alibuda@linux.alibaba.com>,
Dust Li <dust.li@linux.alibaba.com>,
Sidraya Jayagond <sidraya@linux.ibm.com>,
Wenjia Zhang <wenjia@linux.ibm.com>,
Mahanta Jambigi <mjambigi@linux.ibm.com>,
Tony Lu <tonylu@linux.alibaba.com>,
Wen Gu <guwen@linux.alibaba.com>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-s390@vger.kernel.org
Subject: Re: [PATCH net-next v3 2/2] net/smc: handle -ENOMEM from smc_wr_alloc_link_mem gracefully
Date: Thu, 25 Sep 2025 11:40:40 +0200 [thread overview]
Message-ID: <cd1c6040-0a8f-45fb-91aa-2df2c5ae085a@redhat.com> (raw)
In-Reply-To: <20250921214440.325325-3-pasic@linux.ibm.com>
On 9/21/25 11:44 PM, Halil Pasic wrote:
> @@ -836,27 +838,39 @@ int smcr_link_init(struct smc_link_group *lgr, struct smc_link *lnk,
> rc = smc_llc_link_init(lnk);
> if (rc)
> goto out;
> - rc = smc_wr_alloc_link_mem(lnk);
> - if (rc)
> - goto clear_llc_lnk;
> rc = smc_ib_create_protection_domain(lnk);
> if (rc)
> - goto free_link_mem;
> - rc = smc_ib_create_queue_pair(lnk);
> - if (rc)
> - goto dealloc_pd;
> + goto clear_llc_lnk;
> + do {
> + rc = smc_ib_create_queue_pair(lnk);
> + if (rc)
> + goto dealloc_pd;
> + rc = smc_wr_alloc_link_mem(lnk);
> + if (!rc)
> + break;
> + else if (rc != -ENOMEM) /* give up */
> + goto destroy_qp;
> + /* retry with smaller ... */
> + lnk->max_send_wr /= 2;
> + lnk->max_recv_wr /= 2;
> + /* ... unless droping below old SMC_WR_BUF_SIZE */
> + if (lnk->max_send_wr < 16 || lnk->max_recv_wr < 48)
> + goto destroy_qp;
If i.e. smc.sysctl_smcr_max_recv_wr == 2048, and
smc.sysctl_smcr_max_send_wr == 16, the above loop can give-up a little
too early - after the first failure. What about changing the termination
condition to:
lnk->max_send_wr < 16 && lnk->max_recv_wr < 48
and use 2 as a lower bound for both lnk->max_send_wr and lnk->max_recv_wr?
Thanks,
Paolo
next prev parent reply other threads:[~2025-09-25 9:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-21 21:44 [PATCH net-next v3 0/2] net/smc: make wr buffer count configurable Halil Pasic
2025-09-21 21:44 ` [PATCH net-next v3 1/2] " Halil Pasic
2025-09-24 17:27 ` Sidraya Jayagond
2025-09-25 9:27 ` Paolo Abeni
2025-09-25 11:25 ` Halil Pasic
2025-09-27 22:55 ` Halil Pasic
2025-09-28 2:02 ` Dust Li
2025-09-28 2:12 ` Dust Li
2025-09-28 8:39 ` Halil Pasic
2025-09-28 11:42 ` Dust Li
2025-09-28 18:32 ` Halil Pasic
2025-09-26 2:44 ` Guangguan Wang
2025-09-26 10:12 ` Halil Pasic
2025-09-26 10:30 ` Halil Pasic
2025-09-28 3:05 ` Guangguan Wang
2025-09-21 21:44 ` [PATCH net-next v3 2/2] net/smc: handle -ENOMEM from smc_wr_alloc_link_mem gracefully Halil Pasic
2025-09-24 17:28 ` Sidraya Jayagond
2025-09-25 9:40 ` Paolo Abeni [this message]
2025-09-25 15:05 ` Halil Pasic
2025-09-25 15:41 ` Paolo Abeni
2025-09-25 21:46 ` Halil Pasic
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=cd1c6040-0a8f-45fb-91aa-2df2c5ae085a@redhat.com \
--to=pabeni@redhat.com \
--cc=alibuda@linux.alibaba.com \
--cc=dust.li@linux.alibaba.com \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=sidraya@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).