From: Leon Romanovsky <leon@kernel.org>
To: Jacob Moroni <jmoroni@google.com>
Cc: Tatyana Nikolova <tatyana.e.nikolova@intel.com>,
jgg@nvidia.com, linux-rdma@vger.kernel.org,
krzysztof.czurylo@intel.com
Subject: Re: [for-next 00/16] Add RDMA support for Intel IPU E2000 in irdma
Date: Tue, 9 Sep 2025 14:34:37 +0300 [thread overview]
Message-ID: <20250909113437.GE341237@unreal> (raw)
In-Reply-To: <CAHYDg1Taj9PBoHRoNjBJsgmpWWYtkD9P5BHLRJ-BSi+4J6kU_w@mail.gmail.com>
On Wed, Aug 27, 2025 at 03:21:28PM -0400, Jacob Moroni wrote:
> Tested with rdma-unit-test (https://github.com/google/rdma-unit-test).
>
> [==========] 522 tests from 43 test suites ran. (1872510 ms total)
> [ PASSED ] 481 tests.
> [ SKIPPED ] 41 tests, listed below:
>
> Tested-by: Jacob Moroni <jmoroni@google.com>
What did you test?
I don't see any rdma-core changes to support this new driver.
https://lore.kernel.org/all/20250827152545.2056-8-tatyana.e.nikolova@intel.com/
"""
This change introduces a GEN3 auxiliary vPort driver responsible for
registering a verbs device for every RDMA-capable vPort. Additionally,
the UAPI is updated to prevent the binding of GEN3 devices to older
user-space providers.
"""
Thanks
next prev parent reply other threads:[~2025-09-09 11:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 15:25 [for-next 00/16] Add RDMA support for Intel IPU E2000 in irdma Tatyana Nikolova
2025-08-27 15:25 ` [for-next 01/16] RDMA/irdma: Refactor GEN2 auxiliary driver Tatyana Nikolova
2025-08-27 15:25 ` [for-next 02/16] RDMA/irdma: Add GEN3 core driver support Tatyana Nikolova
2025-08-27 15:25 ` [for-next 03/16] RDMA/irdma: Discover and set up GEN3 hardware register layout Tatyana Nikolova
2025-08-27 15:25 ` [for-next 04/16] RDMA/irdma: Add GEN3 CQP support with deferred completions Tatyana Nikolova
2025-08-27 15:25 ` [for-next 05/16] RDMA/irdma: Add GEN3 support for AEQ and CEQ Tatyana Nikolova
2025-08-27 15:25 ` [for-next 06/16] RDMA/irdma: Add GEN3 HW statistics support Tatyana Nikolova
2025-08-27 15:25 ` [for-next 07/16] RDMA/irdma: Introduce GEN3 vPort driver support Tatyana Nikolova
2025-08-27 15:25 ` [for-next 08/16] RDMA/irdma: Add GEN3 virtual QP1 support Tatyana Nikolova
2025-08-27 15:25 ` [for-next 09/16] RDMA/irdma: Extend QP context programming for GEN3 Tatyana Nikolova
2025-08-27 15:25 ` [for-next 10/16] RDMA/irdma: Add support for V2 HMC resource management scheme Tatyana Nikolova
2025-08-27 15:25 ` [for-next 11/16] RDMA/irdma: Support 64-byte CQEs and GEN3 CQE opcode decoding Tatyana Nikolova
2025-08-27 15:25 ` [for-next 12/16] RDMA/irdma: Add SRQ support Tatyana Nikolova
2025-08-27 15:25 ` [for-next 13/16] RDMA/irdma: Restrict Memory Window and CQE Timestamping to GEN3 Tatyana Nikolova
2025-08-27 15:25 ` [for-next 14/16] RDMA/irdma: Add Atomic Operations support Tatyana Nikolova
2025-08-27 15:25 ` [for-next 15/16] RDMA/irdma: Extend CQE Error and Flush Handling for GEN3 Devices Tatyana Nikolova
2025-08-27 15:25 ` [for-next 16/16] RDMA/irdma: Update Kconfig Tatyana Nikolova
2025-08-27 19:21 ` [for-next 00/16] Add RDMA support for Intel IPU E2000 in irdma Jacob Moroni
2025-09-09 11:34 ` Leon Romanovsky [this message]
2025-09-09 13:15 ` Jacob Moroni
2025-09-10 10:07 ` Leon Romanovsky
2025-09-18 9:01 ` Leon Romanovsky
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=20250909113437.GE341237@unreal \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--cc=jmoroni@google.com \
--cc=krzysztof.czurylo@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=tatyana.e.nikolova@intel.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