On Fri, Sep 18, 2020 at 03:34:54PM +0300, Oded Gabbay wrote: > > > Another example is that the submission of WQ is done through our QMAN > > > mechanism and is NOT mapped to userspace (due to the restrictions you > > > mentioned above and other restrictions). > > > > Sure, other RDMA drivers also require a kernel ioctl for command > > execution. > > > > In this model the MR can be a software construct, again representing a > > security authorization: > > > > - A 'full process' MR, in which case the kernel command excution > > handles dma map and pinning at command execution time > > - A 'normal' MR, in which case the DMA list is pre-created and the > > command execution just re-uses this data > > > > The general requirement for RDMA is the same as DRM, you must provide > > enough code in rdma-core to show how the device works, and minimally > > test it. EFA uses ibv_ud_pingpong, and some pyverbs tests IIRC. > > > > So you'll want to arrange something where the default MR and PD > > mechanisms do something workable on this device, like auto-open the > > misc FD when building the PD, and support the 'normal' MR flow for > > command execution. > > I don't know how we can support MR because we can't support any > virtual address on the host. Our internal MMU doesn't support 64-bits. > We investigated in the past, very much wanted to use IBverbs but > didn't figure out how to make it work. > I'm adding Itay here and he can also shed more details on that. I'm not sure what that means, if the driver intends to DMA from process memory then it certainly has a MR concept. MRs can control the IOVA directly so if you say the HW needs a MR IOVA < 2**32 then that is still OK. Jason
