Thanks, Pasha. I see them now.
I asked precisely because I doubted that I have enough understanding of the
code structure to find this code on my own (and I did look). Obviously I
was right to doubt myself.
-Paul
On Mon, Oct 22, 2012 at 7:10 AM, Shamis, Pavel wrote:
> Paul,
>
> Did you look
Okay. How does this sound?
I'm trying to use the Cross Memory Attach (CMA) capability, but am getting:
"mca_btl_sm_get_sync: process_vm_readv
failed: 1." Why am I seeing this error message?
This may be due to insufficient permissions. CMA's usage requirements are
exactly the same as those requi
Ah, I see - I checked and I don't see any unusual behavior in ompi_info or in
picking up the params in components, so it looks like it didn't matter.
On Oct 22, 2012, at 8:04 AM, "Hjelm, Nathan T" wrote:
> The change was due to the removal of the deprecated functions in
> mca_base_param. Comm
The change was due to the removal of the deprecated functions in
mca_base_param. Comments in the command line parser suggested the change was
expected eventually:
179 struct opal_cmd_line_init_t {
180 /** If want to set an MCA parameter, set its type name here.
181
Paul,
Did you look at mca_btl_ugni_put / mca_btl_ugni_get functions in the ugni
btl ?
-Pasha
I am trying to resolve an odd issue I am seeing with my one uGNI-based code,
and was hoping to use OMPI's uGNI support as an example of correct usage. My
particular interest is in RDMA, but as far
