I've been assigned CMR 2728, which is to apply some thread-support
changes to 1.5.x. The trac ticket has amusing language about "needs
testing". I'm not sure what that means. We rather consistently say
that we don't promise anything with regards to true thread support. We
specifically say c
On Mar 8, 2011, at 12:12 , Damien Guinier wrote:
> Hi Jeff
Sorry, your email went on the devel mailing list of Open MPI.
> I'm working on large message exchange optimization. My optimization consists
> in "choosing
> the best protocol for each large message".
> In fact,
> - for each device, th
Hi Jeff
I'm working on large message exchange optimization. My optimization
consists in "choosing
the best protocol for each large message".
In fact,
- for each device, the way to chose the best protocol is different.
- the faster protocol for a given device depends on that device hardware
and
The stack trace indicate that your orted segfaulted in the
orte_odls_base_notify_iof_complete which means it received a message that was
interpreted as a ORTE_DAEMON_IOF_COMPLETE (21). Nothing more to get out from
your output unfortunately.
george.
On Mar 8, 2011, at 08:15 , Hugo Meyer wrote
Hmmmwell, the output indicates both daemons crashed, but doesn't really
indicate where the crash occurs. If you have a core file, perhaps you can get a
line number. Are you perhaps trying to send to someone who died?
One nit: in your vprotocol code, you re-use buffer in the send and recv. Th
Yes, after the release is a break. I'm sending now all my output, maybe that
helps more. But the code is basically the one i sent. The normal execution
reaches to the send/receive between the orted_comm and the receiver.
Best regards.
Hugo
2011/3/8 Ralph Castain
> The comm can most certainly b
The comm can most certainly be done - there are other sections of that code
that also send messages. I can't see the end of your new code section, but I
assume you ended it properly with a "break"? Otherwise, you'll execute whatever
lies below it as well.
On Mar 8, 2011, at 8:19 AM, Hugo Meyer
Yes, i set the value 31 and it is not duplicated.
2011/3/8 Ralph Castain
> What value did you set for this new command? Did you look at the cmds in
> orte/mca/odls/odls_types.h to ensure you weren't using a duplicate value?
>
>
> On Mar 8, 2011, at 6:15 AM, Hugo Meyer wrote:
>
> Hello @ll.
>
>
What value did you set for this new command? Did you look at the cmds in
orte/mca/odls/odls_types.h to ensure you weren't using a duplicate value?
On Mar 8, 2011, at 6:15 AM, Hugo Meyer wrote:
> Hello @ll.
>
> I've got a problem in a communication between the
> v_protocol_receiver_component.c
Hello @ll.
I've got a problem in a communication between
the*v_protocol_receiver_component.c
* and the *orted_comm.c. *
In the *mca_vprotocol_receiver_component_init* i've added a request that is
received correctly by the *orte_daemon_process_commands *but when i try to
reply to the sender i get
There was only 1 very minor change (to the FCA coll) since rc3. We expect to
do minor sanity tests on this tarball and release it as 1.5.2 final.
http://www.open-mpi.org/software/ompi/v1.5/
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/a
11 matches
Mail list logo
