From: Leon Romanovsky <leon@kernel.org>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: jgg@ziepe.ca, Dean Luick <dean.luick@cornelisnetworks.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next 05/23] RDMA/core: Add writev to uverbs file descriptor
Date: Wed, 2 Jul 2025 11:36:31 +0300 [thread overview]
Message-ID: <20250702083631.GI6278@unreal> (raw)
In-Reply-To: <aed06612-2e0f-41ed-a0f7-e9f3c55ce657@cornelisnetworks.com>
On Tue, Jul 01, 2025 at 01:17:48PM -0400, Dennis Dalessandro wrote:
> On 7/1/25 12:04 PM, Leon Romanovsky wrote:
> > On Tue, Jul 01, 2025 at 09:57:23AM -0400, Dennis Dalessandro wrote:
> >> On 7/1/25 8:32 AM, Leon Romanovsky wrote:
> >>> On Mon, Jun 30, 2025 at 11:30:12AM -0400, Dennis Dalessandro wrote:
> >>>> From: Dean Luick <dean.luick@cornelisnetworks.com>
> >>>>
> >>>> Add a writev pass-through between the uverbs file descriptor and
> >>>> infiniband devices. Interested devices may subscribe to this
> >>>> functionality.
> >>>
> >>> Aren't we use IOCTL and not write interface now?
> >>> Why do we need this?
> >>
> >> We wanted to keep all the semantics of the user interface the same so it's an
> >> easy migration to the uverbs cdev from the private cdev. The idea is that all
> >> the command and control is still ioctl, but the "data path" is still using the
> >> writev() to pass in the iovecs.
> >
> > ok, just add this to the commit message.
> >
>
> Will do.
>
> >> By the way I'll get the rdma_core (user space) changes posted soon so you can
> >> see both sides.
> >
> > BTW, I looked whole series and upto MAD/verbs interface everything looks ok.
> > The latter simply broke me with >3K LOC in single patch.
>
> Yeah sorry about all that. The advantage to the new chip is we don't need to do
> all of the MAD stuff in the kernel because it's now done in FW. So most of it is
> just carried over from hfi1. The driver just needs to find out about some
> things. Would it help if I point out the major differences? I could take a crack
> and trying to break that up more even.
It will help if you can separate machine generated code vs. real logic.
MAD patches are not the worst part. For example, this one:
https://lore.kernel.org/all/175129743814.1859400.4253022820082459886.stgit@awdrv-04.cornelisnetworks.com/
3 files changed, 17722 insertions(+)
With a lot of functions like this, with random casting, multiple
parameters without use e.t.c
+static u64 access_sw_pio_drain(const struct cntr_entry *entry,
+ void *context, int vl, int mode, u64 data)
+{
+ struct hfi2_devdata *dd = (struct hfi2_devdata *)context;
+
+ return dd->verbs_dev.n_piodrain;
+}
+static u64 access_sw_ctx0_seq_drop(const struct cntr_entry *entry,
+ void *context, int vl, int mode, u64 data)
+{
+ struct hfi2_devdata *dd = context;
+
+ return dd->ctx0_seq_drop;
+}
>
> -Denny
>
next prev parent reply other threads:[~2025-07-02 8:36 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 15:29 [PATCH for-next 00/23] Migrate to hfi2 driver Dennis Dalessandro
2025-06-30 15:29 ` [PATCH for-next 01/23] RDMA/OPA: Update OPA link speed list Dennis Dalessandro
2025-06-30 15:29 ` [PATCH for-next 02/23] RDMA/rdmavt: Add ucontext alloc/dealloc passthrough Dennis Dalessandro
2025-06-30 15:30 ` [PATCH for-next 03/23] RDMA/rdmavt: Correct multi-port QP iteration Dennis Dalessandro
2025-06-30 15:30 ` [PATCH for-next 04/23] RDMA/rdmavt: Add driver mmap callback Dennis Dalessandro
2025-06-30 15:30 ` [PATCH for-next 05/23] RDMA/core: Add writev to uverbs file descriptor Dennis Dalessandro
2025-07-01 12:32 ` Leon Romanovsky
2025-07-01 13:57 ` Dennis Dalessandro
2025-07-01 16:04 ` Leon Romanovsky
2025-07-01 17:17 ` Dennis Dalessandro
2025-07-02 8:36 ` Leon Romanovsky [this message]
2025-06-30 15:30 ` [PATCH for-next 06/23] RDMA/hfi1: Remove opa_vnic Dennis Dalessandro
2025-07-01 12:38 ` Leon Romanovsky
2025-07-01 13:44 ` Dennis Dalessandro
2025-07-01 16:00 ` Leon Romanovsky
2025-07-01 17:19 ` Dennis Dalessandro
2025-06-30 15:30 ` [PATCH for-next 07/23] RDMA/hfi2: Consolidate ABI files and setup uverbs access Dennis Dalessandro
2025-06-30 15:30 ` [PATCH for-next 08/23] RDMA/hfi2: Start hfi2 driver by basing off of hfi1 Dennis Dalessandro
2025-06-30 15:30 ` [PATCH for-next 09/23] RDMA/hfi2: Add in HW register definition files Dennis Dalessandro
2025-06-30 15:30 ` [PATCH for-next 10/23] RDMA/hfi2: Add in HW register access support Dennis Dalessandro
2025-08-25 14:42 ` Jason Gunthorpe
2025-08-25 16:34 ` Dennis Dalessandro
2025-06-30 15:30 ` [PATCH for-next 11/23] RDMA/hfi2: Add in trace header files Dennis Dalessandro
2025-06-30 15:30 ` [PATCH for-next 12/23] RDMA/hfi2: Add in trace support Dennis Dalessandro
2025-06-30 15:30 ` [PATCH for-next 13/23] RDMA/hfi2: Add system core header files Dennis Dalessandro
2025-08-25 14:42 ` Jason Gunthorpe
2025-06-30 15:30 ` [PATCH for-next 14/23] RDMA/hfi2: Add system core support Dennis Dalessandro
2025-06-30 15:31 ` [PATCH for-next 15/23] RDMA/hfi2: Add in MAD handling related headers Dennis Dalessandro
2025-06-30 15:31 ` [PATCH for-next 16/23] RDMA/hfi2: Implement MAD handling Dennis Dalessandro
2025-06-30 15:31 ` [PATCH for-next 17/23] RDMA/hfi2: Add IO related headers Dennis Dalessandro
2025-06-30 15:31 ` [PATCH for-next 18/23] RDMA/hfi2: Implement data moving infrastructure Dennis Dalessandro
2025-06-30 15:31 ` [PATCH for-next 19/23] RDMA/hfi2: Add in support for verbs Dennis Dalessandro
2025-08-25 14:45 ` Jason Gunthorpe
2025-06-30 15:31 ` [PATCH for-next 20/23] RDMA/hfi2: Support ipoib Dennis Dalessandro
2025-06-30 15:31 ` [PATCH for-next 21/23] RDMA/hfi2: Add misc header files Dennis Dalessandro
2025-06-30 15:31 ` [PATCH for-next 22/23] RDMA/hfi2: Add the rest of the driver Dennis Dalessandro
2025-06-30 15:31 ` [PATCH for-next 23/23] RDMA/hfi2: Make it build 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=20250702083631.GI6278@unreal \
--to=leon@kernel.org \
--cc=dean.luick@cornelisnetworks.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=jgg@ziepe.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox