Unexpected issues with 2 NVME initiators using the same target
Jason Gunthorpe
jgunthorpe at obsidianresearch.com
Mon Jul 10 13:05:22 PDT 2017
On Mon, Jul 10, 2017 at 03:03:18PM -0400, Chuck Lever wrote:
> One option is to somehow split the Send-related data structures from
> rpcrdma_req, and manage them independently. I've already done that for
> MRs: MR state is now located in rpcrdma_mw.
Yes, this is is what I was implying.. Track the SQE related stuff
seperately in memory allocated during SQ setup - MR, dma maps, etc.
No need for an atomic/lock then, right? The required memory is bounded
since the inline send depth is bounded.
Jason
More information about the Linux-nvme
mailing list