Hi, Thanks for the reply , i will look into the get_dma_mr() path for registering memory. And probably get back to all of you for some clarification if i get stuck.
On the same note, 2 things i noticed while using softiwarp: 1. the current version of softiwarp ( from the master git ) doesn't support the latest kernel version (3.0.0 rc4) as it still using the IW_CM_EVENT_STATUS_xxx values that have been removed (https://patchwork.kernel.org/patch/772712/) in the latest kernel iteration. Would you like me to submit a patch as we had to change the code already ? 2: i noticed that sofiwarp crash the kernel when you post a work request with an invalid rkey from userspace . I will try to reproduce the crash and send you some code. Maybe if i have time a patch Regards Benoit On 30 June 2011 17:34, Bernard Metzler <[email protected]> wrote: > > > [email protected] wrote on 06/30/2011 04:19:01 PM: > >> Hi, >> > > maybe i misread your last email - are you trying to use reg_user_mr() > as a kernel client? If yes - that will not work. You should use the > interface as > described by Wendy (get_dma_mr() etc.), since you are dealing with kernel > memory. I can add a check to siw to prevent that call into > siw_reg_user_mr() to be executed for kernel clients. > > thanks, > Bernard. > > >> We are working to create a RDMA client within the kernel which will >> connect to a working RDMA userspace server. >> We are using the userspace code for testing purpose , in the final >> version all the communication will be done within the kernel space. >> > > <snip> > > -- " The production of too many useful things results in too many useless people" -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
