From: Leon Romanovsky <leon@kernel.org>
To: Konstantin Taranov <kotaranov@linux.microsoft.com>
Cc: kotaranov@microsoft.com, snsanghvi@microsoft.com,
longli@microsoft.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH rdma-next v5 00/10] RDMA/mana_ib: Add kernel RC and fast registration support
Date: Sun, 18 Oct 2026 16:05:06 +0300 [thread overview]
Message-ID: <20261018130506.GF64621@unreal> (raw)
In-Reply-To: <20261017064413.995985-1-kotaranov@linux.microsoft.com>
On Fri, Oct 16, 2026 at 11:44:03PM -0700, Konstantin Taranov wrote:
> From: Konstantin Taranov <kotaranov@microsoft.com>
>
> Add kernel RC QPs and fast-registration MRs to the MANA RDMA driver
> for kernel consumers such as NVMe/RDMA and NFS/RDMA.
>
> Implement QP creation and state management, work request posting,
> completion processing, error handling, and queue draining. Kernel RC
> QPs require extended-WQE and power-of-two-SQ hardware support.
>
> Tested with krping, NVMe/RDMA, and NFS/RDMA, including RC send and
> receive error recovery with krping and NVMe/RDMA.
I want to set expectations. This series has Sashiko comments, but you
haven't responded to the previous comments, leaving us unsure whether
they are valid or have been addressed in subsequent revisions. In
addition, the series is too large to be considered for this cycle.
Therefore, it will not be considered for this cycle.
Thanks
prev parent reply other threads:[~2026-10-18 13:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 6:44 [PATCH rdma-next v5 00/10] RDMA/mana_ib: Add kernel RC and fast registration support Konstantin Taranov
2026-10-17 6:44 ` [PATCH rdma-next v5 01/10] RDMA/mana_ib: Allocate and map fast-registration MRs Konstantin Taranov
2026-10-17 6:49 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 02/10] RDMA/mana: Create and destroy kernel RC QPs Konstantin Taranov
2026-10-17 6:52 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 03/10] net/mana: Extend GDMA encoding for new RDMA WQEs Konstantin Taranov
2026-10-17 6:54 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 04/10] RDMA/mana_ib: Maintain kernel RC QP state Konstantin Taranov
2026-10-17 6:48 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 05/10] RDMA/mana_ib: Post receive WRs on kernel RC QPs Konstantin Taranov
2026-10-17 6:48 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 06/10] RDMA/mana_ib: Post send and memory-management WRs on " Konstantin Taranov
2026-10-17 7:00 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 07/10] RDMA/mana_ib: Poll RC completions using PSN and FSN progress Konstantin Taranov
2026-10-17 6:56 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 08/10] RDMA/mana_ib: Flush and notify CQs when kernel QPs enter ERR Konstantin Taranov
2026-10-17 7:12 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 09/10] RDMA/mana_ib: Handle error CQEs for RC QPs Konstantin Taranov
2026-10-17 7:23 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 10/10] RDMA/mana_ib: Drain kernel receive and send queues Konstantin Taranov
2026-10-17 7:01 ` sashiko-bot
2026-10-18 13:05 ` Leon Romanovsky [this message]
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=20261018130506.GF64621@unreal \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=kotaranov@linux.microsoft.com \
--cc=kotaranov@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=snsanghvi@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.