From: Jakub Kicinski <kuba@kernel.org>
To: "D. Wythe" <alibuda@linux.alibaba.com>
Cc: mjambigi@linux.ibm.com, wenjia@linux.ibm.com,
wintera@linux.ibm.com, dust.li@linux.alibaba.com,
tonylu@linux.alibaba.com, guwen@linux.alibaba.com,
davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
leonro@nvidia.com, pabeni@redhat.com, edumazet@google.com,
sidraya@linux.ibm.com, jaka@linux.ibm.com,
oliver.yang@linux.alibaba.com
Subject: Re: [PATCH net-next v4 0/3] net/smc: transition to RDMA core CQ pooling
Date: Tue, 21 Jul 2026 17:53:09 -0700 [thread overview]
Message-ID: <20260721175309.321b6503@kernel.org> (raw)
In-Reply-To: <20260716113745.65234-1-alibuda@linux.alibaba.com>
On Thu, 16 Jul 2026 19:37:42 +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.
There are 2 fixes for SMC on the list waiting for review.
It'd also be great to get someone to review this series, preferably
from IBM. There are 7 reviewers/maintainers for this code.
Pinging y'all is getting really tedious.
next prev parent reply other threads:[~2026-07-22 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 11:37 [PATCH net-next v4 0/3] net/smc: transition to RDMA core CQ pooling D. Wythe
2026-07-16 11:37 ` [PATCH net-next v4 1/3] net/smc: clear the correct v2 slot and buffer in smc_wr_tx_put_slot() D. Wythe
2026-07-22 7:12 ` Mahanta Jambigi
2026-07-16 11:37 ` [PATCH net-next v4 2/3] net/smc: reduce TX slot contention with exclusive wait D. Wythe
2026-07-16 11:37 ` [PATCH net-next v4 3/3] net/smc: transition to RDMA core CQ pooling D. Wythe
2026-07-22 0:53 ` Jakub Kicinski [this message]
2026-07-22 7:06 ` [PATCH net-next v4 0/3] " Mahanta Jambigi
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=20260721175309.321b6503@kernel.org \
--to=kuba@kernel.org \
--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=jaka@linux.ibm.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=oliver.yang@linux.alibaba.com \
--cc=pabeni@redhat.com \
--cc=sidraya@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@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