if you're specifying ib://host:port as your config files, then that should be using native IB interfaces.
To see what transport your client is using, you'll need to look at the pvfs2tab file and see if it says tcp://host:port (for tcp and ipoib) or if it says ib://host:port (for ib) that is what determines the protocol to be used by clients. I have yet to see a situation where ipoib outperforms the native IB, but these results would be very interesting. Can you provide any more information? Kyle xiangyong ouyang wrote: > hi, > > I'm testing pvfs2 over both InfiniBand and IPoIB. For IB, I started pvfs2 > server with config file like ib://hostname:3335.... ForIPoIB, pvfs2 servers > use config file like tcp://ipoib-address.3334..... > > Then I mounted pvfs2 file system accrodingly in clients, using either > ib://hostname:3335 or tcp://ipoib-address:3334... > > After that, I run mpi-io test program on clients to measure R/W bandwidth of > pvfs2. To my surprise the ipoib gives a better performance number than IB, > which can't be true since ipoib involves a lot of overhead on top of IB. > > So I doubt that clients might not be talking to pvfs2 servers using IB or > ipoib as I expect. I want to know what kind of communication transport a > client is using (is it tcp/ip, ipoib or IB). How can I implement that task? > thanks! > > > xiangyong ouyang > > _______________________________________________ > Pvfs2-users mailing list > [email protected] > http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users > > _______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
