ofed

Java Sockets on RDMA (JSOR) vs jVerbs performance in Infiniband

一个人想着一个人 提交于 2019-12-18 18:34:39
问题 I have basic understanding of both JSOR and jVerbs. Both handle limitations of JNI and use fast path to reduce latency. Both of them use user Verbs RDMA interface for avoiding context switch and providing fast path access. Both also have options for zero-copy transfer. The difference is that JSOR still uses the Java Socket interface. jVerbs provides a new interface. jVerbs also has something called Stateful Verbs Call to avoid repeat serialization of RDMA requests which they say reduces

How can I increase OpenFabrics memory limit for Torque jobs?

心不动则不痛 提交于 2019-12-02 07:20:27
问题 When I run MPI job over InfiniBand, I get the following worning. We use Torque Manager. -------------------------------------------------------------------------- WARNING: It appears that your OpenFabrics subsystem is configured to only allow registering part of your physical memory. This can cause MPI jobs to run with erratic performance, hang, and/or crash. This may be caused by your OpenFabrics vendor limiting the amount of physical memory that can be registered. You should investigate the

Java Sockets on RDMA (JSOR) vs jVerbs performance in Infiniband

本小妞迷上赌 提交于 2019-11-30 16:51:46
I have basic understanding of both JSOR and jVerbs. Both handle limitations of JNI and use fast path to reduce latency. Both of them use user Verbs RDMA interface for avoiding context switch and providing fast path access. Both also have options for zero-copy transfer. The difference is that JSOR still uses the Java Socket interface. jVerbs provides a new interface. jVerbs also has something called Stateful Verbs Call to avoid repeat serialization of RDMA requests which they say reduces latency. jVerbs provides a more native interface and applications can directly use these. I read the jVerbs