[ofw] post send in kernel mode

[Tzachi Dar]

As for the second question, if the buffers are locked into user space
than when the process dies the kernel driver gets a notification and can
free the memory and close the qps.

The first question is harder. I believe that by default this will not
work. I guess that if the memory used by the qps and cqs will be mapped
to kernel  as well than writing to it will have the same effect as in
user (this probably needs new code in the kernel driver). Still the
memory that is posted will also have to be registered in the hca. Please
note that we also have to make sure that when there is a completion on
the cq a kernel function will be called.

But if I understand your logic than what you realy have is a process in
user mode. This process wants to send data. I think that what you want
to do is 1) move from user to kernel. 2) register the data with the hca
(fmr?) or copy it to an already registered buffer. 3) send the data.
What advantage does this have over sending directly from the user?

Thanks
Tzachi

-----Original Message-----
From: ofw-bounces at lists.openfabrics.org
[mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Sean Hefty
Sent: Monday, August 24, 2009 8:47 PM
To: 'Richard Frank'
Cc: ofw at lists.openfabrics.org
Subject: RE: [ofw] post send in kernel mode

>Sean, if  QPs and CQs are created via librdmacm ala winverbs... 
>assuming that the associated doorbells and mailboxes created for these 
>objects are mapped into user mode - can these objects (doorbells) also 
>be directly accessed from kernel mode ?

Someone from Mellanox needs to answer this.

Btw - what process would create these resources, and what if it dies?

_______________________________________________
ofw mailing list
ofw at lists.openfabrics.org
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw