*assumption* that the
process will never move and might be able to use the native x86 timer (there's
some complications here, but we might be able to figure it out). Bad Things
could happen if the process ever moved, though (e.g., if the application ever
manually changed the binding).
--
similar that I have
> found had to do with different version of OpenMPI installed, but I only have
> one version, and I believe it is the one being used.
>
> Thank you,
> Kalin
> _______
> users mailing list
> us...@op
ese out prior to the release.
Ralph is just going through the pain right now of upgrading to Autoconf 2.68 /
Libtool 2.4; hopefully we'll have fixes on the trunk RSN for the
newest-of-the-new autotools.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
libmpi.so
explicitly listed in the link line, which should contain MPI_Abort. Can you nm
on that file and ensure that it is actually listed there?
VT guys -- any ideas here?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
On Oct 14, 2010, at 5:38 PM, Jed Brown wrote:
> $ nm -D
> /home/jed/src/openmpi-1.5/bclang/ompi/contrib/vt/vt/../../../.libs/libmpi.so
> |grep MPI_Abort
> 00074380 T PMPI_Abort
>
> In contrast, with gcc:
>
> $ nm -D
> /home/jed/src/openmpi-1.5/bgcc/ompi/contrib/vt/vt/../../../.libs/li
to highly optimize the
send-to-self case, but it should perform well.
You might want to benchmark memcpy vs. MPI_Sendrecv() to self (for example) and
see if there's a noticeable difference.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ould allow more flexibility when writing MPI programs
> in Fortran90.
>From my understanding of Fortran, that would violate the MPI spec.
You could, I think, use an array subsection when you call MPI_STARALL that
would give you a 1D array of integers, right?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
mo' betta than the
existing MPI F90 bindings. We plan to prototype the F08 module in OMPI when we
finish specifying it in the Forum, and revamp the F90 support in OMPI at
more-or-less the same time.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
the rendered text.
>
> -- Jeremiah Willcock
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisc
NING: *** This configure script does not support
> --program-prefix, --program-suffix or --program-transform-name. Users
> are recommended to instead use --prefix with a unique directory and make
> symbolic links as desired for renaming." >&2;}
>
> If I remove the new contr
______
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
on otherwise-empty machines?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ssue on my side.
>
> --td
>
>
> On 10/21/2010 06:47 AM, Terry Dontje wrote:
>> On 10/21/2010 06:43 AM, Jeff Squyres (jsquyres) wrote:
>>> Also, i'm not entirely sure what all the commands are that you are showing.
>>> Some of those warnings (eg in config.lo
t on code A seems to run faster. I do have a
> lot of communications in code B too. It involves 500 procs. I had thought
> code B should have no effect on the time spent on code A if I use MPI_Barrier.
>
> Linbao
> On Thu, Oct 21, 2010 at 5:17 AM, Jeff Squyres wrote:
> On O
27;MPI::Win::Free()' and
> 'undefined reference to 'MPI::Datatype::Free()'
>
> So could I get some help? Thanks!
>
> _______
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailma
gt; What is the possible reason ?
>
>
> Any help is appreciated.
>
> thanks
>
> jack
>
> Oct. 22 1010
> _______
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
x27;m a little suspect of what you sent already (e.g., you didn't
include the waitall, which is kinda important :-) ).
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
gt;
> How to get the ZOMBIE_PID ?
>
> "ps" from the command line, or getpid() from C code.
>
> Jed
>
> ___ users mailing list
> us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users
>
be
> > > better in a non-interactive environment.
> > >
> > > Where should I put the (gdb --batch -ex 'bt full' -ex 'info reg' -pid
> > > ZOMBIE_PID) in the script ?
> > >
> > > Is control returning to your script after rank
ive] Error 1
>
>
> Any idea as to how to go around fixing this? Any help would be greatly
> regarded, since I'm supposed to meet a deadline, and half of my semester has
> been spent trying to get either LAM-MPI or Open MPI (which I was suggested I
> shift to) to wor
; is incompatible with i386 output
>>>
>>>>> /usr/bin/ld: final link failed: Invalid operation
>>>
>>>>> collect2: ld returned 1 exit status
>>>
>>>>> make[2]: *** [libopen-pal.la] Error 1
>>>
>>>>> make[2]: Leaving directory `/home/wolf/Downloads/openmpi-1.5/opal'
>>>
>>>>> make[1]: *** [all-recursive] Error 1
>>>
>>>>> make[1]: Leaving directory `/home/wolf/Downloads/openmpi-1.5/opal'
>>>
>>>>> make: *** [all-recursive] Error 1
>>>
>>>>>
>>>
>>>>>
>>>
>>>>> Any idea as to how to go around fixing this? Any help would be greatly
>>>>> regarded, since I'm supposed to meet a deadline, and half of my semester
>>>>> has been spent trying to get either LAM-MPI or Open MPI (which I was
>>>>> suggested I shift to) to work.
>>>
>>>>> Thank you very much.
>>>
>>>>>
>>>
>>>>> Regards,
>>>
>>>>> Saahil___
>>>
>>>> users mailing list
>>>
>>>> us...@open-mpi.org
>>>
>>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>
>>>
>>>
>>>
>>>
>>> ___
>>>
>>> users mailing list
>>>
>>> us...@open-mpi.org
>>>
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
who *needs* the functionality represented by
those still-open tickets?
Thanks for your input.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
GSMRvd0MeLbp1HWJTbVYlCwo=
> =NwEP
> -END PGP SIGNATURE-
>
> _______
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
des and libmpi.so from
v1.4.3 on other nodes). This is absolutely not guaranteed to work -- we don't
even try to maintain this kind of compatibility.
Does that make sense?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
FLAGS to the configure script?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
On Nov 2, 2010, at 4:57 AM, jody wrote:
> So i guess the basic question is:
> is it permitted to rename openMPI installations, and if yes how is
> this porperly done (since a simple mv doesn't work)
Yes: http://www.open-mpi.org/faq/?category=building#installdirs
--
Jeff
**
> ** This warning was added by the IU Computer Science Dept. mail scanner. **
> *
>
>
>
> ___
> users mailing list
>
polling.
We've had many discussions about this topic, but have never really addressed it
-- the need for low latency has been greater than the need for
blocking/not-consuming-CPU progress.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
website; obtained via the src.rpm download)
>
> --Jim
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ve them
>> installed in their own /opt/opemmpi-gcc, etc directories).
>> Any suggestions how to proceed? (the specific version of openmpi in
>> this case is the one available for download on Nov 2 from the main
>> website; obtained via the src.rpm download)
>>
-CW-MPI-Mechanic.pdf
:-)
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
doing. Ahem. But seriously, I try to use printf's for
only truly trivial things; I use various kinds of debugging tools for
everything else (e.g., I'll frequently use gdb to examine corefiles and/or
attach to individual processes in parallel jobs to do heavy-lifting debugging).
--
Jef
f OpenMPI, and it seems to correctly support my
> existing software.
>
> So, now for my question:
>
> Should FCFLAGS show up on these links lines and, if so, how would I get
> 64-bit objects?
>
> Thanks,
>
> Brian Price
>
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
rian Price
>
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
e parameter is not being set in cases of oversubscription,
> with or without an explicit hostfile.
>
> Jed
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsq
mca_pml_ob1.so
> #7 0xf7ed9c60 in PMPI_Send () from /home/gmaj/openmpi/lib/libmpi.so.0
> #8 0x0804e900 in main ()
> --
>
> If anybody knows what may cause this problem or what may I do to find
> the reason, any help is appreciated.
>
> My open-mpi is version 1.4.1.
>
>
> Regards,
> Grzegorz Maj
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
>
> --
> David Zhang
> University of California, San Diego
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
and eth2 are the same on both hosts (i.e., eth1 on hostA is
reachable by eth1 on hostB; ditto for eth2).
See the FAQ for more details on other ways of setting MCA parameters
(environment vars, files, etc.).
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
branch that has much better debug/error
messages, but I've never had the time to finish it (indeed, I think there's a
bug in that development branch right now, otherwise I'd recommend giving it a
whirl). :-\
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
the Forum's
deliberations on MPI-3.
http://sc10.supercomputing.org/schedule/event_detail.php?evid=bof122
Many other Open MPI organizations who will also have a presence at SC; be sure
to stop by their booths and say hello.
See you there!
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal
can I
> find what the error codes mean?
>
> Thanks,
> Ondrej Marsalek
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
_
>>> users mailing list
>>> us...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
me_res.end());
>
>std::cout << "Total time: " << total_time << " secs\n"
> << "MPI_Test calls: " << time_res.size() << '\n'
> << std::fixed << std::setprecision(10)
e differnece between these two versions, or
> what affects the "SYSTEM CPU" and execution speed?
There shouldn't be any noticeable difference in performance between these
versions.
Assumedly you're running your tests on otherwise-idle machines. Is the
difference
m_name environment-modules' --define
> 'build_all_in_one_rpm 0' --define 'configure_options
> --with-tm=/opt/torque' --define '_name openmpi-gcc' openmpi-1.4.3.spec
Weird -- you're saying that *without* --enable-contrib-no-build=vt, the 1.4.3
SRPM fails
asiliy G Tolstov
> Selfip.Ru
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
4.lib(broadcast.obj) : error LNK2001: unresolved
> external symbol _MPI_Bcast@20
>
>
> is boostpro's mpi lib against openmpi or another MPI implementation?
>
>
> regards,
>
> ___
> users mailing list
> us...@open-
tallation. You
should contact your IB vendor for assistance.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
larger. MPI
should do the Right Thing under the covers in this case.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
> Anyway, if it's just a mistake, please fix it in the next version.
>
> Regards,
> Tetsuya Mishima
>
> _______
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
to write a custom code to do that.
MPI doesn't necessarily mean SPMD -- you can certainly have the GUI call
MPI_INIT and then call MPI_COMM_SPAWN to launch a different executable to do
the compute working stuff.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ticular, could it be that the size of the message actually
> received by MPI_Recv() does not match `size` (the variable)?
No.
> In case a shorter message (different from the one initially matched)
> was received, can I get the actual message size via a new call to
> MPI_Get_count(&mpi
MCA sds: seed (MCA v1.0, API v1.0, Component v1.2.7)
> MCA sds: singleton (MCA v1.0, API v1.0, Component v1.2.7)
> MCA sds: slurm (MCA v1.0, API v1.0, Component v1.2.7)
>
> Can anyone please look at the files and tell me what to do?
>
> Tushar
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ices Tel (ext): +44(0)113 343 5429
> University of Leeds, LS2 9JT, UK
> -
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
install-recursive] Error 1
>
>
>
> --
> Maurício Paulo Rodrigues
> Bacharelando em Física
> Universidade Federal de Viçosa
> Mobile- (32)-9972 2239
> e-mail alternativo mauricio.pa...@ufv.br
> Brazil
> _______
> users mailin
#x27;d estimate the Feburary timeline, although
ROMIO will likely come into the OMPI trunk in the "near future" (i.e., Bull is
actively working on it -- I just sent some comments on their patch earlier
today).
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
h
es. The new processes will need to call MPI_COMM_GET_PARENT to get the
intercommunicator that is shared with the parent process(es).
Make sense? Read through the MPI spec section on "dynamic processes" for more
details.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
e meek. You need to have
different executables for your different OS's, for example.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ter (linux)
With Open MPI, correct -- we don't currently support "MPI talk" between Windows
and Linux. Sorry! :-(
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
roups be able to have a
starting rank of 0 and be able to use MPI_COMM_SIZE to find how many peers are
in your subgroup. Having distinct sub-communicators is helpful here.
That being said... (this can go on ad nauseam -- it just depends on your app
and whether you want to do the splitting or not; ther
___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
>
> --
> Maurício Paulo Rodrigues
> Bacharelando em Física
> Universidade Federal de Viçosa
> Mobile- (32)-9972 2239
> e-mail
find
icc (after it had assumedly been able to find it all the way up until that
point -- i.e., it must have been able to find icc when it installed/re-linked
libopen-pal.so).
On Nov 30, 2010, at 8:35 AM, Tim Prince wrote:
> On 11/29/2010 3:03 PM, Gus Correa wrote:
>> Jeff
t;>> if(putchar(getchar()) < 0)
>>>> break;
>>>> }
>>>>
>>>> MPI_Finalize ();
>>>>
>>>> return (0);
>>>> }
>>>>
>>>>
>>>> Thank you,
>>>>
>>>> Jesse Ziser
>>>> Applied Research Laboratories:
>>>> The University of Texas at Austin
>>>> ___
>>>> users mailing list
>>>> us...@open-mpi.org
>>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>
>>>
>>> ___
>>> users mailing list
>>> us...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
lls allowed" flag, and then goes and calls some mpi
> routines to clean up the opened files:
Rob -- I think you're right.
I'll file a ticket, but I don't know exactly when this will be addressed.
James; if you can find a good solution and send a patch, that would
anything.
> maybe www.open-mpi.org can publish a openmpi's document to explain those
> args and principle.
We are lacking in the documentation department; contributions would be greatly
appreciated...
The README file has a bunch about BTLs; that may be helpful reading.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
n.o
> /usr/lib/gcc/x86_64-linux-gnu/3.4.6/../../../../lib/libfrtbegin.a(frtbegin.o):
> dans la fonction ▒ main ▒:
> (.text+0x1e): référence indéfinie vers ▒ MAIN__ ▒
> collect2: ld a retourné 1 code d'état d'exécution
>
> Thanks,
> Benjamin
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
rr
>>>
>>> i = 32768
>>> i2 = 2*i
>>> allocate(buf(i,i2))
>>> count = i*i2
>>> buf = 1
>>> call MPI_Send(buf, count, MPI_INTEGER, dest, tag, MPI_COMM_WORLD, mpierr)
>>>
>>> Now count is 2^31 which overflows a 32bit intege
ence, when we talk about the 2B count limit, we're referring to the fact that
most systems where MPI is used default to 4 byte int's.
> I may have inadvertently misled Benjamin, if this perception is wrong.
> I will gladly stand corrected, if this is so.
>
> You are the OpenM
> mpirun -x DISPLAY=:0.0 -np 4 -hostfile ~/openmpi.hosts ./myapp
>>> >
>>> > I've tried adding the -d option with no success.
>>> >
>>> > Does anyone have any suggestions or comments? I'll certainly provide
>>> > more information if required.
>>> >
>>> > Thanks,
>>> > Brad
>>> > ___
>>> > users mailing list
>>> > us...@open-mpi.org
>>> > http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>
>>>
>>> ___
>>> users mailing list
>>> us...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>
>>> ___
>>> users mailing list
>>> us...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
dress of your MPI data, but things may be
> different in the general case. Again, my adivce would be to post a
> question in a dedicated C++ forum for a comprehensive answer.
>
> If you are going to send C++ classes via MPI, you might want to have a
> look at Boost.MPI, whic
>> Any clarifications?
>>
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
t; On Dec 13, 2010, at 7:31 AM, Jeff Squyres wrote:
>
>> Also note that recent versions of the Linux kernel have changed what
>> sched_yield() does -- it no longer does essentially what Ralph describes
>> below. Google around to find those discussions.
>>
>>
>&
inue to see near 100% utilization even if we yield because
> we will always poll for some time before deciding to yield.
>
>
> On Dec 13, 2010, at 7:52 AM, Jeff Squyres wrote:
>
>> See the discussion on kerneltrap:
>>
>> http://kerneltrap.org/Linux/CFS_and_sche
e -- read this
thread all the way through (the Linux sched_yield() discussion is near the end):
https://lists.mcs.anl.gov/mailman/htdig/mpich-discuss/2007-September/002711.html
On Dec 13, 2010, at 10:52 AM, Jeff Squyres wrote:
> I think there *was* a decision and it effectively changed
...etc.).
We developers have previously discussed how to make the MPI layer block
(instead of busy poll), but there has never been a compelling need to do so.
Specifically, conversion to allow a blocking model is a fair amount of complex
work that no one has allocated any time/resources to do
already brought up.
There seems to be general desire for this kind of functionality both within the
Forum and among users, so we'll see where it goes...
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
program that b) uses
MPI_THREAD_SINGLE and c) only uses MPI from one thread.
Technically, that's not what the standard says, though -- MPI_THREAD_SINGLE is
supposed to be used only with single-threaded applications.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
BTL; looks like we
should also harden this up for the TCP OOB as well...
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
?
Have a look at this paper:
http://www.open-mpi.org/papers/euro-pvmmpi-2007-ib/
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
nsoft.
Can you verify that you're using the "right" mpif77 (and friends) when you
intend to, and so on?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
hesitate to use the word "spike" when dealing with such small numbers in TCP
traffic). And they could be due to a lot of different things, many of which
are beyond OMPI's control.
Have you seen if this has any impact on your actual application performance?
--
Jeff Squ
d due to OS issues.
Have you eliminated all other sources of jitter? Are you binding to specific
cores? Have you turned off all unused daemons? Do you see the same behavior
with shared memory transport (which should make jitter issues more pronounced)?
...etc.
--
Jeff Squyres
jsquy...@cisc
he
> above work fine, though the windows are only on a subset of the
> communicated array, and the origin data is being PUT from part of the
> array that is not within the window.
> _________
> Matt
>
>
>
> _
the Web, unfortunately, looking MPI or IPM ways :-)
>
> Thanks in advance for any hint, Regards, G.
>
>
> _______
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
>>>
>>>
>>> ___
>>> users mailing list
>>> us...@open-mpi.org <mailto:us...@open-mpi.org>
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>
>>
>>
>>
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
hiers attachés qu'il contient
> sont confidentiels et destinés exclusivement à l'usage de la personne
> à laquelle ils sont adressés. Si vous avez reçu ce message par erreur,
> merci d'en avertir immédiatement son émetteur et de ne pas en conserver
> de copie.
>
> This e-mail and any files transmitted with it are confidential and
> intended solely for the use of the individual to whom they are addressed.
> If you have received this e-mail in error please inform the sender
> immediately, without keeping any copy thereof.
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
re's 2 MCA params:
oob_tcp_port_min_v4 (default: 0)
oob_tcp_port_range_v4 (default: 65536)
Try setting these values to mutually exclusive ranges for each of your jobs and
see if that fixes the problem. Keep in mind that user-level ports start at
1024, so your lowest range might as well st
value was set by setting an
environment variable, then you can just getenv() it. But if the value was set
some other way (e.g., via a file), it won't necessarily be loaded in the
environment.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ases in which it has made a significant difference?
>
>
> On 12/15/10 9:18 PM, "Jeff Squyres" wrote:
>
>> Is there a reason to convert your code from send/receive to put/get?
>>
>> The performance may not be that significantly different, and as you have
>>> Can anyone point me towards the most recent documentation for using
>>>>>>>>>>> srun and openmpi?
>>>>>>>>>>>
>>>>>>>>>>> I followed what i found on the web with enabling the MpiPorts co
-32/10.9/lib -Wl,-soname
> -Wl,libopen-pal.so.1 -o .libs/libopen-pal.so.1.0.0
>
>
>
> Best wishes,
>
> Paul
>
>
>
>
>
>
> --
> Dipl.-Inform. Paul Kapinos - High Performance Computing,
> RWTH Aachen University, Center for Co
related to messages over
>> ethernet?
>>
>> Thanks just trying to get some clarification.
>>
>> Brock Palen
>> www.umich.edu/~brockp
>> Center for Advanced Computing
>> bro...@umich.edu
>> (734)936-1985
>>
>>
>
Computing,
> RWTH Aachen University, Center for Computing and Communication
> Seffenter Weg 23, D 52074 Aachen (Germany)
> Tel: +49 241/80-24915
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
_SUCCESS )
> printf("[%d] I get the connection with %s at %s !\n",myrank, service,
> port_name_clt);
> MPI_Errhandler_set(MPI_COMM_WORLD, MPI_ERRORS_ARE_FATAL);
> }
>
> if(myrank != 0) *srv = 0;
>
> return gcom;
>
> }
>
>
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
eginner, -platform specific ,
> -compilation issues, -performance ...
True. I think the challenge will be to find people who can staff these
channels.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
___
>>> users mailing list
>>> us...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>
>>
>> ___
>> users mailing list
>>
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
> --
> Cordialement, Gilbert.
>
> --
> *-*
> Gilbert Grosdidier
> gilbert.grosdid...@in2p3.fr
>
> LAL / IN2P3 / CNRS Phone : +33 1 6446 8909
> Faculté des Sciences, Bat. 200 Fax : +33 1 6446 8546
> B.P. 34, F-91898 Orsay Cedex (FRANCE)
> *-*
>
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
er-core ?
>>>>
>>>> george.
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
; - Andy Ball
>>
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
API. See
OMPI's README file for details.
> 6) What's mean of "CPC" in ompi?
Connect Psuedo Component. :-)
It's one of those things that's probably best left as an acronym. ;-)
(meaning: I can explain what it means if you care, but it's mainly boring
201 - 300 of 4582 matches
Mail list logo
