> I just started working with librdmacm and I was wondering if there is a
> specific reason why rdma_reg_* functions and rdma_post_send/write functions
> take the local memory address as non-const pointer "void * addr". These
> functions shouldn't and don't change the memory pointed to by addr. I t
Hi,
I just started working with librdmacm and I was wondering if there is a
specific reason why rdma_reg_* functions and rdma_post_send/write functions
take the local memory address as non-const pointer "void * addr". These
functions shouldn't and don't change the memory pointed to by addr. I t
On 11/27/13 13:16, Hal Rosenstock wrote:
On 11/15/2013 7:15 AM, Line Holen wrote:
The retry counter is now only updated if a packet is actually sent.
(But as before the initial request is also counted.)
Prior to this change the actual maximum number of packets sent were
polling retry number min
Hi Matan,
Le mercredi 27 novembre 2013 à 10:21 +0200, Matan Barak a écrit :
> On 27/11/2013 12:02 AM, Yann Droneaud wrote:
...
> > INIT_UDATA(&udata, buf + sizeof cmd,
> > - (unsigned long) cmd.response + sizeof resp,
> > + (void __user *)(unsigned long)cmd.response +
On 11/15/2013 7:15 AM, Line Holen wrote:
> The retry counter is now only updated if a packet is actually sent.
> (But as before the initial request is also counted.)
>
> Prior to this change the actual maximum number of packets sent were
> polling retry number minus one.
>
> Signed-off-by: Line H
On 27/11/2013 12:02 AM, Yann Droneaud wrote:
Hi,
Please find a patchset against create_flow/destroy_flow and
associated extended command scheme.
These are fixes that must be applied before making the new uverbs
widely available.
This patchset gather some patches already sent independently:
- T
On 27/11/2013 12:02 AM, Yann Droneaud wrote:
Currently, INIT_UDATA() does an implicit cast to a pointer,
so that 'response' address, eg. output buffer, can be used
as is to initialize a struct ib_udata:
do {\
(udata)->
