On Wed, Jul 08, 2015 at 06:03:37PM -0600, Jason Gunthorpe wrote: > The major trouble with that is that the new MR types work by posting > work to the send queue, that work creates the MR. > > I don't know all the details of how those schemes work, but it doesn't > look like it fits into this model ? It sorta does, but we do need a QP argument. I have implemented this abstraction in a driver, but it's still usign driver specific data structures at this point, so extracting all the arguments is a bit of a mess. But if there is some interest I can try to polish it up and port an existing driver or two to it. Note that post_send isn't really used for alloating the MR structure but performing the registration. > Maybe if rdma_register_sg was the only API and it accepted a QP, under > the hood it could re-use a pooled/create a non-queued (F)MR, or issue > FRMR, or work with indirect? I really want to avoid another allocator in my driver. With the blk-mq model we basically preallocate a request with all resoruces, so right now I totally avoid allocations in I/O path, which is something I'd like to keep if possible. -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
