The major benefit of the second method is that it has the obvious potential to
save us some memory. Not much I guess, but somewhere in the order of few Kb.
But in order to save this memory, the originator must keep a pointer to the
data in order to be able to free it after the mca_params framewo
What: Update OMPI_CHECK_LUSTRE to link against only -llustreapi. From what I
can tell we do not need to link against -llustre. Also remove
--with-lustre-libs option.
Why: Some platforms do not have liblustre and we shouldn't need to link against
liblustre anyway.
When: I need some feedback fro
Notes:
Variable system currently takes ownership of string values. This is done so
strings can be freed when overwritten (by mca_base_var_set_value) or when the
variable is deregistered. This requires that initial string values be allocated
on the heap (not .DATA, heap, etc). Brian raised a goo
Yeah, that's the quandary: I can see both use cases.
That's why I proposed the "nowarn:" syntax that George hated. :-)
Got any other suggestion on how to handle both use cases?
On Feb 5, 2013, at 7:25 AM, "Barrett, Brian W" wrote:
> I guess I can see that, but I have the opposite use case;
I guess I can see that, but I have the opposite use case; I have a device
on some nodes and not others that I want to ignore, so I set
btl_tcp_if_exclude to include that device. It would be totally
counter-intuitive to have a giant warning because of that.
Brian
On 2/5/13 6:46 AM, "Jeff Squyres
I had a typo in my btl_tcp_if_exclude such that it was effectively
mpirun --mca btl_tco_if_exclude bogus ...
instead of ignoring the actual interface I wanted to ignore. And since I
wasn't ignoring the special loopback device that I have on some machines, every
single MPI job hung because th
