All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: leon@kernel.org, Dean Luick <dean.luick@cornelisnetworks.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Douglas Miller <doug.miller@cornelisnetworks.com>,
	Breandan Cunningham <brendan.cunningham@cornelisnetworks.com>,
	linux-rdma@vger.kernel.org
Subject: Re: [PATCH v2 for-next 00/24] Migrate to hfi2 driver
Date: Mon, 29 Jun 2026 14:58:47 -0300	[thread overview]
Message-ID: <20260629175847.GA7525@ziepe.ca> (raw)
In-Reply-To: <178257721001.371918.6610421101075283586.stgit@awdrv-04>

On Sat, Jun 27, 2026 at 12:24:54PM -0400, Dennis Dalessandro wrote:
> While sharing similar bones, the chip for the Cornelis Networks next
> generation fabric technology has some fundamental differences that
> resulted in a near complete re-write of the driver. It also does not
> use the private cdev interface that the hfi1 driver exposes. After
> discussing this with the RDMA maintainers we have decided to go with
> the approach of moving to a new driver and declaring hfi1 obsolete.
> 
> It is desirable to keep hfi1 around temporarily to let user APIs
> catch up to support access through the uverbs device rather than the
> private hfi1 cdev.
> 
> This driver is designed to support future products as well.
> 
> This series applies on top of the rdma/for-next branch.
> 
> This series will be followed up to pick up any remaining changes from
> hfi1 that were not yet incorporated in our internal development tree.
> 
> Changelogs in individual patches but the highligths are as follows…

You are going to have to go through a fix the relavent sashiko
things. There sure are alot :\

https://sashiko.dev/#/patchset/178257721001.371918.6610421101075283586.stgit%40awdrv-04

Jason

  parent reply	other threads:[~2026-06-29 17:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27 16:24 [PATCH v2 for-next 00/24] Migrate to hfi2 driver Dennis Dalessandro
2026-06-27 16:24 ` [PATCH v2 for-next 01/24] RDMA/hfi2: Start hfi2 driver by basing off of hfi1 Dennis Dalessandro
2026-06-27 16:25 ` [PATCH v2 for-next 02/24] RDMA/hfi2: Add in HW register definition files Dennis Dalessandro
2026-06-27 16:25 ` [PATCH v2 for-next 03/24] RDMA/hfi2: Add counter accessor functions Dennis Dalessandro
2026-06-27 16:25 ` [PATCH v2 for-next 04/24] RDMA/hfi2: Add in HW register access support Dennis Dalessandro
2026-06-27 16:25 ` [PATCH v2 for-next 05/24] RDMA/hfi2: Add in trace header files Dennis Dalessandro
2026-06-27 16:25 ` [PATCH v2 for-next 06/24] RDMA/hfi2: Add in trace support Dennis Dalessandro
2026-06-27 16:25 ` [PATCH v2 for-next 07/24] RDMA/hfi2: Add system core header files Dennis Dalessandro
2026-06-27 16:25 ` [PATCH v2 for-next 08/24] RDMA/hfi2: Add driver and interrupt infrastructure Dennis Dalessandro
2026-06-27 16:25 ` [PATCH v2 for-next 09/24] RDMA/hfi2: Add initialization and firmware support Dennis Dalessandro
2026-06-27 16:25 ` [PATCH v2 for-next 10/24] RDMA/hfi2: Add in MAD handling related headers Dennis Dalessandro
2026-06-27 16:25 ` [PATCH v2 for-next 11/24] RDMA/hfi2: Add cport management Dennis Dalessandro
2026-06-27 16:25 ` [PATCH v2 for-next 12/24] RDMA/hfi2: Implement MAD handling Dennis Dalessandro
2026-06-27 16:26 ` [PATCH v2 for-next 13/24] RDMA/hfi2: Add IO related headers Dennis Dalessandro
2026-06-27 16:26 ` [PATCH v2 for-next 14/24] RDMA/hfi2: Add PIO send infrastructure Dennis Dalessandro
2026-06-27 16:26 ` [PATCH v2 for-next 15/24] RDMA/hfi2: Add SDMA infrastructure Dennis Dalessandro
2026-06-27 16:26 ` [PATCH v2 for-next 16/24] RDMA/hfi2: Implement data moving infrastructure Dennis Dalessandro
2026-06-27 16:26 ` [PATCH v2 for-next 17/24] RDMA/hfi2: Add verbs core Dennis Dalessandro
2026-06-27 16:26 ` [PATCH v2 for-next 18/24] RDMA/hfi2: Add RC protocol support Dennis Dalessandro
2026-06-27 16:26 ` [PATCH v2 for-next 19/24] RDMA/hfi2: Add in support for verbs Dennis Dalessandro
2026-06-27 16:26 ` [PATCH v2 for-next 20/24] RDMA/hfi2: Add misc header files Dennis Dalessandro
2026-06-27 16:26 ` [PATCH v2 for-next 21/24] RDMA/hfi2: Add the rest of the driver Dennis Dalessandro
2026-06-27 16:26 ` [PATCH v2 for-next 22/24] RDMA/hfi2: Make it build and add TODO list Dennis Dalessandro
2026-07-05 14:14   ` Leon Romanovsky
2026-06-27 16:26 ` [PATCH v2 for-next 23/24] RDMA/hfi2: Modernize mmap to use rdma_user_mmap_entry infrastructure Dennis Dalessandro
2026-06-27 16:26 ` [PATCH v2 for-next 24/24] RDMA/hfi2: Support ipoib Dennis Dalessandro
2026-06-29 17:58 ` Jason Gunthorpe [this message]
2026-06-30 16:15   ` [PATCH v2 for-next 00/24] Migrate to hfi2 driver Dennis Dalessandro

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=20260629175847.GA7525@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=arnd@arndb.de \
    --cc=brendan.cunningham@cornelisnetworks.com \
    --cc=dean.luick@cornelisnetworks.com \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=doug.miller@cornelisnetworks.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    /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.