Last I looked the OpenIB BTL relied on the short eager rdma buffers
being written in order? Is this still the case?
If so, how is this handled when iWARP is underneath the User Verb API
and not Mellonox IB HCAs?
On Jul 9, 2008, at 4:08 PM, Don Kerr wrote:
Last I looked the OpenIB BTL relied on the short eager rdma buffers
being written in order? Is this still the case?
The eager rdma optimization relies on the last byte of the short
message being written last. I.e., when we see the last byte in
I have been investigating Ticket #1135 - stdin is read twice if rank=0
shares the node with mpirun. Repairing this problem is going to be quite
difficult due to the rather terrible spaghetti code in the IOF, and the fact
that the IOF in the HNP actually rml.sends the IO to itself multiple times
as
I'd like to have a look at the diff between the two, but I can't do so
until tomorrow at the earliest.
On Jul 9, 2008, at 7:26 PM, Ralph Castain wrote:
I have been investigating Ticket #1135 - stdin is read twice if rank=0
shares the node with mpirun. Repairing this problem is going to be
q
v1.3 RMs: Due to some recent work, the MCA parameter
mpi_paffinity_alone disappeared -- it was moved and renamed to be
opal_paffinity_alone. This is Bad because we have a lot of historical
precent based on the MCA param name "mpi_paffinity_alone" (FAQ, PPT
presentations, e-mails on public
