The client loads the RDMA plug in via a module loader. To try it out use
perftest or latencytest
use the option: -P [ --protocol ] tcp|rdma
on the broker, use --load-module to load the RMDA module.
these are both single file clients, so you can look what is needed to
update any qpid C++ client for
RDMA by looking at these clients.
The RDMA support is native OFED, broker can listen on more than one
transport at the same time.
RDMA will be included in the M4 release, code freeze Oct 22 I believe is
the date M4 close down. release
then after that once committers are happy with it.
Carl.
Hello,
I'm with the Network-Based Computing Lab at Ohio State University. Our
lab primarily does research with the Message Passing Interface (MPI) over
interconnects like InfiniBand and RDMA. Recently we have started
evaluating/testing Qpid with the TCP adaptations to InfiniBand (Sockets
Direct Protocol [SDP] and IP over InfiniBand [IPoIB]).
We would like to know more about where the Qpid project plans to go with
RDMA. Could anyone give me a brief overview and anticipated timeline of
the planned functionality? I've noticed some RDMA-related code submissions to
the C++ trunk
this month by Andrew Stitcher. I've been able to run the C++ broker
listening for RDMA via the RdmaIOPlugin class (at least according to the
broker log). However, how does the client side work? Does the
RdmaConnector class integrate with the client's Connection class? Also in
src/tests I've noticed that "rdma" is an option for the ConnectionOptions
class. How will this class fit into the scheme of things?
Thanks in advance for any info,
Greg Marsh
Network-Based Computing Lab
Ohio State University
[EMAIL PROTECTED]
http://nowlab.cse.ohio-state.edu/
