Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Mahanta Jambigi <mjambigi@linux.ibm.com>
To: Jakub Kicinski <kuba@kernel.org>, "D. Wythe" <alibuda@linux.alibaba.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Dust Li <dust.li@linux.alibaba.com>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Sidraya Jayagond <sidraya@linux.ibm.com>,
	Wenjia Zhang <wenjia@linux.ibm.com>,
	Simon Horman <horms@kernel.org>,
	Tony Lu <tonylu@linux.alibaba.com>,
	Wen Gu <guwen@linux.alibaba.com>,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-s390@vger.kernel.org, netdev@vger.kernel.org,
	oliver.yang@linux.alibaba.com, pasic@linux.ibm.com
Subject: Re: [PATCH net-next 0/2] net/smc: transition to RDMA core CQ pooling
Date: Fri, 12 Jun 2026 10:40:33 +0530	[thread overview]
Message-ID: <da211ad9-5da0-4c22-a738-c602a8a1532e@linux.ibm.com> (raw)
In-Reply-To: <20260602140359.3b97d180@kernel.org>



On 03/06/26 2:33 am, Jakub Kicinski wrote:
> On Thu, 28 May 2026 16:48:17 +0800 D. Wythe wrote:
>> This series transitions SMC-R completion handling to RDMA core CQ pooling
>> via the ib_cqe API. The new completion model improves scalability by
>> allowing per-link completion processing across multiple cores and enables
>> DIM-based interrupt moderation.
>>
>> As a side effect, the increased concurrency can amplify contention for TX
>> slots on the shared wait queue. Patch 2 addresses this by switching TX slot
>> allocation from non-exclusive wait_event() to prepare_to_wait_exclusive(),
>> which avoids thundering-herd wakeups under contention.
>>
>> Patch 1 replaces the global per-device CQ and manual tasklet polling model
>> with RDMA core CQ pooling.
>> Patch 2 reduces TX slot contention by using exclusive wait queue entries
>> during allocation.
> 
> Sashiko reports a couple of issues on patch 1:
> https://sashiko.dev/#/patchset/20260528084819.6059-2-alibuda@linux.alibaba.com
> Are these legit?
> 
> Either way - would be good to get some reviews here from (ohter) SMC
> maintainers.

D Wythe - Thank you for addressing Sashiko's comments.

I've reviewed the three issues raised by Sashiko for Patch 1 and your
responses:

Issue #1: Acknowledged, will be fixed in v3. I agree with your proposal
of using "max_send_wr = 3 * lnk->lgr->max_send_wr + *3*;"
Issue #2: I agree this is a pre-existing issue unrelated to this patch
series. The potential memory leak and NULL pointer de-reference in
smc_wr_tx_put_slot() should be addressed in a separate patch to keep the
scope focused.
Issue #3: Acknowledged, will be fixed in v3. I agree that ib_drain_qp()
introduced in this patch does open a UAF window.

I am looking forward for v3.

  parent reply	other threads:[~2026-06-12  5:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28  8:48 [PATCH net-next 0/2] net/smc: transition to RDMA core CQ pooling D. Wythe
2026-05-28  8:48 ` [PATCH net-next v2 1/2] " D. Wythe
2026-06-04  8:36   ` Paolo Abeni
2026-06-05  4:00     ` D. Wythe
2026-05-28  8:48 ` [PATCH net-next v2 2/2] net/smc: reduce TX slot contention with exclusive wait D. Wythe
2026-06-08 14:04   ` Dust Li
2026-06-02 21:03 ` [PATCH net-next 0/2] net/smc: transition to RDMA core CQ pooling Jakub Kicinski
2026-06-05  3:29   ` D. Wythe
2026-06-12  5:10   ` Mahanta Jambigi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-08  6:37 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=da211ad9-5da0-4c22-a738-c602a8a1532e@linux.ibm.com \
    --to=mjambigi@linux.ibm.com \
    --cc=alibuda@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=dust.li@linux.alibaba.com \
    --cc=edumazet@google.com \
    --cc=guwen@linux.alibaba.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oliver.yang@linux.alibaba.com \
    --cc=pabeni@redhat.com \
    --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