Interesting. My best guess is that the OMPI libraries aren't being found,
though I'm a little surprised because the error message indicates an inability
to malloc - but it's possible the message isn't accurate.
One thing stands out - I see you compiled your program with "javac". I suspect
that
Hi
> (taking the liberty of moving this thread to the devel list...)
>
> On Dec 19, 2012, at 9:22 AM, Siegmar Gross wrote:
>
> >> I think the real shortcoming is that there is no Datatype.Resized
> >> function. That can be fixed.
> >
> > Are you sure? That would at least solve one problem.
>
I can argue the opposite: in the most general case, each process will exchange
data with all other processes, so a blocking approach as implemented in the
current version make sense. As you noticed, this lead to poor results when the
exchange pattern is sparse. We took what we believed is the mo
Corey,
The communication pattern looks legit, it is very difficult to see what is
going wrong with a code to look at. Can you provide a simple case (maybe the
skeleton of your application) we can work from?
George.
On Dec 20, 2012, at 22:07 , Corey Allen wrote:
> Hello,
>
> I am trying t
Oops! The times that were sent were wrong. Here's the correct times:
- 3:00am-09:00am Pacific US time
- 4:00am-10:00am Mountain US time
- 5:00am-11:00am Central US time
- 6:00am-12:00am Eastern US time
- 11:00am-05:00pm GMT
On Dec 21, 2012, at 12:44 PM, Jeff Squyres wrote:
> Our Indiana U. ho
Hi
> Hmmm...weird. Well, it looks like OMPI itself is okay, so the issue
> appears to be in the Java side of things. For whatever reason, your
> Java VM is refusing to allow a malloc to succeed. I suspect it has
> something to do with its setup, but I'm not enough of a Java person
> to point you t
Our Indiana U. hosting providers will be doing some maintenance over the
holiday break.
All Open MPI services -- web, trac, SVN, ...etc. -- will be down on Wednesday,
December 26th, 2012 during the following time period:
- 5:00am-11:00am Pacific US time
- 6:00am-12:00pm Mountain US time
- 7:00a
Hmmm...weird. Well, it looks like OMPI itself is okay, so the issue appears to
be in the Java side of things. For whatever reason, your Java VM is refusing to
allow a malloc to succeed. I suspect it has something to do with its setup, but
I'm not enough of a Java person to point you to the probl
Hi
> I can't speak to the other issues, but for these - it looks like
> something isn't right in the system. Could be an incompatibility
> with Suse 12.1.
>
> What the errors are saying is that malloc is failing when used at
> a very early stage in starting the process. Can you run even a
> C-bas
I can't speak to the other issues, but for these - it looks like something
isn't right in the system. Could be an incompatibility with Suse 12.1.
What the errors are saying is that malloc is failing when used at a very early
stage in starting the process. Can you run even a C-based MPI "hello" p
I completely understand there's no "one size fits all", and I appreciate
that there are workarounds to the change in behaviour. I'm only trying
to make what little contribution I can by questioning the architecture
of the pairwise algorithm.
I know that for every user you please, there will be
On 18 December 2012 22:04, Stephen Conley wrote:
> Hello,
>
> ** **
>
> I have installed CMake version 2.8.10.2 and OpenMPI version 1.6.2 on a 64
> bit Windows 7 computer.
>
> ** **
>
> OpenMPI is installed in “C:\program files\OpenMPI” and the path has been
> updated to include the bin
Hi
I'm still using "Open MPI: 1.9a1r27668" and Java 1.7.0_07. Today I
implemented a few programs to broadcast int, int[], double, or
double[]. I can compile all four programs without problems, which
means that "Object buf" as a parameter in "MPI.COMM_WORLD.Bcast"
isn't a problem for basic datatype
13 matches
Mail list logo
