[OMPI devel] RFC: new btl descriptor flags

2011-11-29 Thread Nathan Hjelm
We need an accurate way to detect if prepare_src/prepare_dst are being called for a get or a put operation. I propose adding two new flags to the btl descriptor (and passing them from ob1/csum/etc): #define MCA_BTL_DES_PUT 0x0010 #define MCA_BTL_DES_GET 0x0020 Comments? Suggestions? Objections

Re: [OMPI devel] RFC: new btl descriptor flags

2011-11-29 Thread George Bosilca
These two functions target at defining a memory layout (contiguous or not) that can be target for a one-sided communication. I don't see why there is a need to know what type of communication that will be … What is so different in the xpmem that requires the memory to be prepared based on the op

Re: [OMPI devel] RFC: new btl descriptor flags

2011-11-29 Thread Nathan Hjelm
On Tue, 29 Nov 2011, George Bosilca wrote: These two functions target at defining a memory layout (contiguous or not) that can be target for a one-sided communication. I don't see why there is a need to know what type of communication that will be … What is so different in the xpmem that re

Re: [OMPI devel] RFC: new btl descriptor flags

2011-11-29 Thread George Bosilca
On Nov 29, 2011, at 15:52 , Nathan Hjelm wrote: > > > On Tue, 29 Nov 2011, George Bosilca wrote: > >> These two functions target at defining a memory layout (contiguous or not) >> that can be target for a one-sided communication. I don't see why there is a >> need to know what type of commun

Re: [OMPI devel] RFC: new btl descriptor flags

2011-11-29 Thread Rolf vandeVaart
This may seem trivial, but should we name them: #define MCA_BTL_DES_FLAGS_PUT 0x0010 #define MCA_BTL_DES_FLAGS_GET 0x0020 Although I see there is some inconsistency in how these flags are named, two of the three original ones have "BTL_DES_FLAGS" in them. Rolf rvandeva...@nvidia.com 781-275-5