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 Feb 20, 2008 3:01 PM, Jeff Squyres wrote:
> On Feb 19, 2008, at 10:12 AM, Sharon Melamed wrote:
>
> I guess I was torn between reporting num_processors/sockets and
> max_socket|core_id. Really, you need both, right? It is possible
> that the number of processors and/or sockets are not contigu
On Feb 19, 2008, at 10:12 AM, Sharon Melamed wrote:
In the patch you sent the variables: num_processors, num_sockets and
num_cores are lost outside the paffinity framework.
I need those in the ODLS framework. what do think about the attached
patch?
I guess I was torn between reporting num_pr
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
