01 Nov, 2011

1 commit


26 May, 2011

1 commit

  • The RDMA CM currently infers the QP type from the port space selected
    by the user. In the future (eg with RDMA_PS_IB or XRC), there may not
    be a 1-1 correspondence between port space and QP type. For netlink
    export of RDMA CM state, we want to export the QP type to userspace,
    so it is cleaner to explicitly associate a QP type to an ID.

    Modify rdma_create_id() to allow the user to specify the QP type, and
    use it to make our selections of datagram versus connected mode.

    Signed-off-by: Sean Hefty
    Signed-off-by: Roland Dreier

    Sean Hefty
     

21 Oct, 2010

1 commit


09 Sep, 2010

2 commits


28 Apr, 2010

1 commit


23 Apr, 2010

1 commit

  • In the original code, the "goto out" calls "rdma_destroy_id(cm_id);"
    That isn't needed here and would cause problems because "cm_id" is an
    ERR_PTR. The new code just returns directly.

    Signed-off-by: Dan Carpenter
    Acked-by: Andy Grover
    Signed-off-by: David S. Miller

    Dan Carpenter
     

17 Mar, 2010

2 commits


24 Aug, 2009

1 commit

  • Enable the building of transports as modules.

    Also, improve consistency of Kconfig messages in relation to other
    protocols, and move build dependency on IB from the RDS core code
    to the rds_rdma module.

    Signed-off-by: Andy Grover
    Signed-off-by: David S. Miller

    Andy Grover
     

06 Aug, 2009

1 commit

  • Elsewhere the sin_family field holds a value with a name of the form
    AF_..., so it seems reasonable to do so here as well. Also the values of
    PF_INET and AF_INET are the same.

    The semantic patch that makes this change is as follows:
    (http://coccinelle.lip6.fr/)

    //
    @@
    struct sockaddr_in sip;
    @@

    (
    sip.sin_family ==
    - PF_INET
    + AF_INET
    |
    sip.sin_family !=
    - PF_INET
    + AF_INET
    |
    sip.sin_family =
    - PF_INET
    + AF_INET
    )
    //

    Signed-off-by: Julia Lawall
    Signed-off-by: David S. Miller

    Julia Lawall
     

20 Jul, 2009

1 commit


10 Apr, 2009

1 commit


27 Feb, 2009

1 commit

  • Although most of IB and iWARP are separated from each other,
    there is some common code required to handle their shared
    CM listen port. This code listens for CM events and then
    dispatches the event to the appropriate transport, either
    IB or iWARP.

    Signed-off-by: Andy Grover
    Signed-off-by: David S. Miller

    Andy Grover