Okay, please see r29052 - I believe this will address everyone's concerns.
Please give it a test so we can verify it is clean - it worked for me, but I
can't test all environments
On Aug 20, 2013, at 7:35 AM, Ralph Castain wrote:
> The error messages already output the name of the other proc,
Thanks!
On Aug 20, 2013, at 11:25 AM, Joshua Ladd wrote:
> All,
>
> As requested, I have placed a simple shmem test code, ‘hello_shmem.c’ in the
> ‘examples’ directory of my Bitbucket repo. It actually does a bit more than
> just “hello world”; this code will “gently” exercise
> start_pes/p
All,
As requested, I have placed a simple shmem test code, 'hello_shmem.c' in the
'examples' directory of my Bitbucket repo. It actually does a bit more than
just "hello world"; this code will "gently" exercise
start_pes/put/get/barrier/shmem_finalize.
Josh
From: devel-boun...@open-mpi.org [
On Aug 20, 2013, at 12:57 PM, Steve Wise wrote:
> You won't let me forget. ;) I will do it.
Awesome, thanks.
>> Specifically: At some point iWARP support will break because we'll be
>> removing
>> ompi/mca/btl/openib/cpc and exclusively using ompi/mca/common/ofacm.
>
> When is this going to
>
> Don't forget that Chelsio is still on the hook for adding iWARP support into
ompi/mca/common/ofacm,
> however. :-)
>
You won't let me forget. ;) I will do it.
> Specifically: At some point iWARP support will break because we'll be removing
> ompi/mca/btl/openib/cpc and exclusively using om
On Aug 20, 2013, at 12:08 PM, Steve Wise wrote:
>> Thank you for tracking this down!
>
> U R welcome. :)
Don't forget that Chelsio is still on the hook for adding iWARP support into
ompi/mca/common/ofacm, however. :-)
Specifically: At some point iWARP support will break because we'll be rem
> -Original Message-
> From: Jeff Squyres (jsquyres) [mailto:jsquy...@cisco.com]
> Sent: Tuesday, August 20, 2013 11:07 AM
> To: Steve Wise
> Cc: Open MPI Developers; Indranil Choudhury
> Subject: Re: [OMPI devel] openmpi-1.7.2 fails to use the RDMACM CPC
>
> I think you hit the nail on
I think you hit the nail on the head -- we typo'ed the macro name in the C
code. Doh!
If you can confirm that this fixes the issue for you, please commit and CMR.
Thank you for tracking this down!
On Aug 20, 2013, at 11:06 AM, Steve Wise wrote:
> So is this the correct fix?
>
> [root@r9 om
So is this the correct fix?
[root@r9 ompi-trunk]# svn diff
Index: ompi/mca/btl/openib/btl_openib_component.c
===
--- ompi/mca/btl/openib/btl_openib_component.c (revision 29050)
+++ ompi/mca/btl/openib/btl_openib_component.c (working
The error messages already output the name of the other proc, so that should be
available. Besides, I just spent all yesterday afternoon auditing our MPI
layers memory usage byte-by-byte and getting my ears burned about the need to
reduce that footprint - not really thrilled about adding to it.
Ah:
Here's the config.log:
configure:133950: checking whether IBV_LINK_LAYER_ETHERNET is declared
configure:133950: gcc -std=gnu99 -c -g -Wall -Wundef -Wno-long-long
-Wsign-compare
-Wmissing-prototypes -Wstrict-prototypes -Wcomment -pedantic
-Werror-implicit-function-declaration
-finline-funct
On Aug 20, 2013, at 10:06 AM, Steve Wise wrote:
> What is the correct fix then? I've never worked with any of this AC stuff...
>
> With the existing code (prior to my broken fix), HAVE_IBV_LINK_LAYER_ETHERNET
> does not get defined.
> Yet the enum and the link_type field are in verbs.h...
Wh
> -Original Message-
> From: Jeff Squyres (jsquyres) [mailto:jsquy...@cisco.com]
> Sent: Tuesday, August 20, 2013 8:59 AM
> To: Steve Wise
> Cc: Open MPI Developers; Indranil Choudhury
> Subject: Re: [OMPI devel] openmpi-1.7.2 fails to use the RDMACM CPC
>
> On Aug 20, 2013, at 9:51 AM,
On Aug 20, 2013, at 9:51 AM, Steve Wise wrote:
> I checked in the correct fix,
Er, no. Please re-read my email -- your fix was incorrect (you're overriding
the output of an AC macro). :-)
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/abo
> Thanks for finding r27212. It was about a year ago, and had clearly fallen
> out of my cache (I
have very
> little to do with the openib BTL these days).
>
> Your solution isn't correct, because HAVE_IBV_LINK_LAYER_ETHERNET is defined
> (nor not) via this m4
> macro in config/ompi_check_ope
If we don't want to lose the usefulness of the error messages (and don't care
that much about the memory requirements), we can initialize this value with the
string of the rank of the process in MPI_COMM_WORLD (instead of NULL). We will
at least get an idea where to start looking in case of trou
16 matches
Mail list logo
