On Wed, Feb 20, 2008 at 04:08:46PM -0500, George Bosilca wrote:
> So I tracked this issue and it seems that the new behavior was
> introduced one year ago by the commit 12433. Starting from this commit,
Except that the log message of this commit says:
Fix regression from v1.1.
1) make the
So I tracked this issue and it seems that the new behavior was
introduced one year ago by the commit 12433. Starting from this
commit, there was no pipeline in the RDMA protocol. That make sense as
we usually don't use NetPipe all the time to check the performances of
the message logging (w
On Tue, Feb 19, 2008 at 10:40:46PM -0500, George Bosilca wrote:
> Actually, it restores the original behavior. The RDMA operations were
> pipelined before the r15247 commit, independent of the fact that they
> had mpool or not. We were actively using this behavior in the message
> logging fra
Actually, it restores the original behavior. The RDMA operations were
pipelined before the r15247 commit, independent of the fact that they
had mpool or not. We were actively using this behavior in the message
logging framework to hide the cost of the local storage of the
payload, and we we
On Tue, Feb 19, 2008 at 02:13:30PM -0500, George Bosilca wrote:
> Few days ago during some testing I realize that the RDMA pipeline was
> disabled for MX and Elan (I didn't check for the others). A quick look
> into the source code, pinpointed the problem into the pml_ob1_rdma.c
> file, and i
Few days ago during some testing I realize that the RDMA pipeline was
disabled for MX and Elan (I didn't check for the others). A quick look
into the source code, pinpointed the problem into the pml_ob1_rdma.c
file, and it seems that the problem was introduced by commit 15247.
The problem c
