10 Apr, 2009

1 commit

  • Currently the recv ring low water mark is 1/4 the depth. Performance
    measurements show that this limits iWARP throughput by flow controlling
    the rds-stress senders. Setting it to 1/2 seems to max the T3
    performance. I tried even higher levels but that didn't help and it
    started to increase the rds thread cpu utilization.

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

    Steve Wise
     

27 Feb, 2009

1 commit

  • Support for iWARP NICs is implemented as a separate
    RDS transport from IB. The code, however, is very
    similar to IB (it was forked, basically.) so let's keep
    it in one changeset.

    The reason for this duplicationis that despite its similarity
    to IB, there are a number of places where it has different
    semantics. iwarp zcopy support is still under development,
    and giving it its own sandbox ensures that IB code isn't
    disrupted while iwarp changes. Over time these transports
    will re-converge.

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

    Andy Grover