Hi Open MPI developers,
I and my coworkers checked mpi-f90-interfaces.h against MPI 2.2 standard
and found many bugs in it. Attached patches fix them for trunk.
Though some of them are trivial, others are not so trivial.
So I'll explain them below.
1. incorrect parameter types
Two trivial para
On 4/3/12 11:08 AM, "Jeffrey Squyres" wrote:
>On Apr 3, 2012, at 11:44 AM, Barrett, Brian W wrote:
>
>> There is discussion of attempting to have a developers meeting this
>> summer. We haven't had one in a while and people thought it would be
>>good
>> to work through some of the ideas on how t
On Apr 3, 2012, at 11:44 AM, Barrett, Brian W wrote:
> There is discussion of attempting to have a developers meeting this
> summer. We haven't had one in a while and people thought it would be good
> to work through some of the ideas on how to implement features for 1.7.
> We don't have a locati
I would like to propose Oak Ridge as a potential location for the meeting.
Pavel (Pasha) Shamis
---
Application Performance Tools Group
Computer Science and Math Division
Oak Ridge National Laboratory
On Apr 3, 2012, at 11:44 AM, Barrett, Brian W wrote:
> Hi all -
>
> There is discussion o
Hi all -
There is discussion of attempting to have a developers meeting this
summer. We haven't had one in a while and people thought it would be good
to work through some of the ideas on how to implement features for 1.7.
We don't have a location yet, but possibilities include Los Alamos and San
Hi all -
Ralph and I put together a list of MPI conformance (against the 2.1, 2.2,
and 3.0 documents). Could you please take a look at the list and either
add items you think are missing, claim items you are working on, or mark
items as complete.
https://svn.open-mpi.org/trac/ompi/wiki/MPIConf
Of course !!! ;)
First set coll_tuned_use_dynamic_rules to 1, and then use
coll_tuned_dynamic_rules_filename to specify a file containing the selection
logic. This is kind of tricky to write, so we don't advertise it to widely. I
added an example below, contact me privately if you need more i
Is there a way to specify collective depending on the size of the message
and number of processes?
Regards,
Pavel Mezentsev
2012/4/3 George Bosilca
> Roswan,
>
> There a re simpler solutions to achieve this. We have a built-in mechanism
> to select a specific collective implementation. Here is
Roswan,
There a re simpler solutions to achieve this. We have a built-in mechanism to
select a specific collective implementation. Here is what you have to add in
your .openmpi/mca-params.conf (or as MCA argument on the command line):
coll_tuned_use_dynamic_rules = 1
coll_tuned_bcast_algorithm
Looks like you didn't set your LD_LIBRARY_PATH to point to where OMPI was
installed, so the individual component libs couldn't be loaded. From the
below, it looks like you need to add /usr/local to your path.
On Mon, Apr 2, 2012 at 7:26 PM, Benedict Holland <
benedict.m.holl...@gmail.com> wrote:
Performance depends on the network topology & node hardware, and the
benchmark - so we don't have enough information to determine the root
of the issue...
However, you can do some debugging on your end (once you master the
techniques you will be able to debug all sorts of performance problems
- no
11 matches
Mail list logo
