https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-9164 Lustre <p>Start using these RDMA APIs and delete the ko2iblnd equivalents:</p> <ul> <li>ib_dma_unmap_single()</li> <li>ib_dma_map_single()</li> <li>ib_dma_mapping_error()</li> </ul> <p>These three routines represent a new strategy for memory pools so there is a lot of ko2iblnd routines which will no longer be needed when these 3 calls get utilized.  Code which maps/unmaps memory and pool creation routines all need to be evaluated and deleted if no longer needed.</p> LU-9164

Incorporate RDMA map/unmap APIs into ko2iblnd

Technical task LU-8874 Major Open Unresolved Amir Shehata Doug Oucharek lnet Mon, 27 Feb 2017 23:10:07 +0000 Fri, 5 Jul 2019 15:12:18 +0000 Lustre 2.10.0 Upstream Upstream 0 8 <p>Whenever I ask questions about the RDMA API, I am told it is not documented so just do what the iSer driver does.  Sigh.</p> <p>James: would you agree that we should "duplicate" the iSer driver's iser_memory.c approach to differentiating between fmr and fastreg and how it makes use of the new RDMA calls?  Doing this would get us away from being "so different" from the other RDMA users who all seem to just copy iSer anyway.  We would keep our existing runtime model (i.e. our scheduler), but would get us to use the RDMA data structures in exactly the same way as iSer.</p> Blocker Related LU-12511 Development Rank 1|hzz593: Rank (Obsolete) 9223372036854775807