what underlying compiler command is being executed under
> the covers."
>
> Regards
> Ahsan
>
> On Tue, Jun 26, 2012 at 6:20 PM, Jeff Squyres wrote:
> Sorry, this looks like an application issue -- i.e., the linker error you're
> getting doesn't look
90/mpif77 --showme,
> Fortran 77 version worked finally,
> but Fortran 90 version still has the problem.
>
> Error: There is no specific subroutine for the generic 'mpi_init' at (1)
>
> any idea??
>
> From: Jeff Squyres
> To: Mohamad Ali Rostami
> Cc: Ope
r=/tmp/bogus/include --libdir=/tmp/bogus/lib64
--libexecdir=/tmp/bogus/libexec --localstatedir=/tmp/bogus/var
--sharedstatedir=/tmp/bogus/var/lib --mandir=/tmp/bogus/share/man
--infodir=/tmp/bogus/share/info
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
; "_name" like this, so if there's an easier way, I'd be happy to do it.
>> I just haven't found anything yet, and haven't yet found the place in
>> the spec file where it's being set to "/opt/openmpi" again.
>>
>> We're probabl
u should not need to do this for Open MPI.
I suspect that there is something else going on.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
differently. But _prefix should definitely give me more
> flexibility as to where it's installed.
...OIC. Forgot about that. :-)
Yeah, I guess you will need to muck with name and/or _name. I don't know the
ramifications of doing that, though.
--
Jeff Squyres
jsquy...@cisco.com
For
.11
> 2) 28.23
> 3) 34.81
>
> That's rather disappointing, isn't it?
Yes, it is. But #2 is not really comparable with #1 and #3. It's quite
possible that with newer IB hardware, the eager limit should be bumped up by
default.
I leave this to Mellanox to figure out
uf=0x14c9da10 "",
> count=0x626eb0, datatype=, op=0x626ec0, comm= optimized out>,
> ierr=0x7fff1376e530) at pallreduce_f.c:77
> #7 0x0049dbd4 in dmumps_142 (id=...) at dmumps_part5.F:5570
>
>
> Thanks.
>
> Willia
> _____
then
> mpi_int_type=MPI_INTEGER8
> else
> mpi_int_type=MPI_INTEGER4
> endif
I don't think that this should be necessary -- as long as you configured OMPI
with the 8-byte-integer setting, then MPI_INTEGER should represent an 8 byte
integer.
--
Jeff Squyres
jsquy...@cisco.com
For
o-select the
MX MTL when you have machines with MX, and when you're on machines that do not
have MX but do have OpenFabrics devices, it should auto-select the openib BTL.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
t; data-for-system-tests/ecoli-MiSeq/MiSeq_Ecoli_MG1655_110527_R1.fastq \
> data-for-system-tests/ecoli-MiSeq/MiSeq_Ecoli_MG1655_110527_R2.fastq
>
>
>
> Sébastien Boisvert
> ___
> 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/
, AMD
> x86-64, version 1 (SYSV), not stripped
>
>
>
> Jeff Squyres a écrit :
>> Yes, PSM is the native transport for InfiniPath. It is faster than the
>> InfiniBand verbs support on the same hardware.
>>
>> What version of Open MPI are you using?
>>
&
what I can tell. Am I
> doing things wrong?
Yoinks, I'm sorry -- that's not quite what I meant. I meant remove the *BTL*
plugin, not the *MTL* plugin.
I.e., if *only* the MX MTL is there, there should be no conflict between the
two (per that bug you and George found), and you should b
is the MX BTL plugin, right?
>
> On Fri, Jun 29, 2012 at 11:16 AM, Jeff Squyres wrote:
>> On Jun 29, 2012, at 2:14 PM, Yong Qin wrote:
>>
>>> Thanks Jeff for the doc. However I'm not sure if I understand your
>>> following comment correctly.
IN, OUT, 1, MPI_2INTEGER, MPI_MINLOC,
> & COMM, IERR)
>
> The compiler options will take care of IN be INTEGER*8, but will
> it do the same for MPI_2INTEGER in the C side
>
> Thanks.
>
> Regards,
>
> William
>
>
>
> Date: Fri, 29 J
; ThxJohn
>>>
>>> ___
>>> 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/
emulate it well enough (e.g., PSM does it all in software, as does MXM).
> It seems to me that ob1 and BTLs are mature and that BTLs self and sm are
> quite
> useful and bug-free for what I know. New code should only do the case when
> the two
> MPI processes are on different no
process. I.e.,
it's basically a busy loop checking network devices (etc.) to see if anything
has happened. Hence, the CPU will likely run at 100%.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ed memory exhaustion in most cases (it falls
back to send/recv in that case), but due to OMPI's lazy wire up, it can still
happen later (e.g., late in an application you do an MPI_SEND to a new
recipient, but it can't allocate a new QP because it's out of registered
memory).
It turn
ation
> is in addition, but tutorials can be attended independently of the
> conference.
>
> General Chair:
> Jack Dongarra
>
> Program chairs and local organizers:
> Siegfried Benkner, University of Vienna
> Jesper Larsson Träff, Vienna University of Technology
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
> the job at least for me.
>
> Thanks' for the prompt fix.
>
> Yves Secretan
> yves.secre...@ete.inrs.ca
>
> Avant d'imprimer, pensez à l'environnement
>
>
> -Message d'origine-
> De : users-boun...@open-mpi.org [mailto:use
e likely to be more bugs than just this one.
I did file https://svn.open-mpi.org/trac/ompi/ticket/3163 about this problem,
though, and will look into it. But possibly not until next week...
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
gt;> deb packages), a subtile compilation options
>> of openMPI, or a bad network configuration ?
>>
>> Regards.
>>
>> B. S.
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.o
t;cpp" CXXCPP="cpp" \
>>> CPPFLAGS="" CXXCPPFLAGS="" \
>>> C_INCL_PATH="" C_INCLUDE_PATH="" CPLUS_INCLUDE_PATH="" \
>>> OBJC_INCLUDE_PATH="" MPIHOME="" \
>>> --without-udapl --without-openib \
>>> --enable-mpi-f90 --with-mpi-f90-size=small \
>>> --enable-heterogeneous --enable-cxx-exceptions \
>>> --enable-orterun-prefix-by-default \
>>> --with-threads=posix --enable-mpi-thread-multiple \
>>> --enable-opal-multi-threads \
>>> --with-hwloc=internal --with-ft=LAM --enable-sparse-groups \
>>> |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.32_cc
>>>
>>> Thank you very much for any help in advance.
>>>
>>>
>>> Kind regards
>>>
>>> Siegmar
>>>
>>> ___
>>> 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/
s to make Open MPI work correctly, even in the face of tiny
amounts of registered memory. I'm not sure we have it right yet, but there are
some things I can ask you to try. I'll reply in more detail on devel.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
ht
t;> 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/
;>>>> Node: node65.cl.corp.com
>>>>>>>
>>>>>>> when attempting to start process rank 0.
>>>>>>> --
>>>>>>>
>>>>>>> 4 total processes failed to start
>>>>>>>
>>>>>>>
>>>>>>> [hammond@node65 bin]$ ./mpirun -np 4 --num-sockets 2 --npersocket 4
>>>>>>> hostname node65.cl.corp.com node65.cl.corp.com node65.cl.corp.com
>>>>>>> node65.cl.corp.com
>>>>>>> [hammond@node65 bin]$
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Jul 16, 2012, at 12:56 PM, Ralph Castain wrote:
>>>>>>>
>>>>>>>> Jeff is at the MPI Forum this week, so his answers will be delayed.
>>>>>>>> Last I
>>>>>> heard, it was close, but no specific date has been set.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Jul 16, 2012, at 11:49 AM, Michael E. Thomadakis wrote:
>>>>>>>>
>>>>>>>>> When is the expected date for the official 1.6.1 (or 1.6.2 ?) to be
>>>>>>>>> available ?
>>>>>>>>>
>>>>>>>>> mike
>>>>>>>>>
>>>>>>>>> On 07/16/2012 01:44 PM, Ralph Castain wrote:
>>>>>>>>>> You can get it here:
>>>>>>>>>>
>>>>>>>>>> http://www.open-mpi.org/nightly/v1.6/
>>>>>>>>>>
>>>>>>>>>> On Jul 16, 2012, at 10:22 AM, Anne M. Hammond wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> For benchmarking, we would like to use openmpi with
>>>>>>>>>>> --num-sockets 1
>>>>>>>>>>>
>>>>>>>>>>> This fails in 1.6, but Bug Report #3119 indicates it is changed in
>>>>>>>>>>> 1.6.1.
>>>>>>>>>>>
>>>>>>>>>>> Is 1.6.1 or 1.6.2 available in tar.gz form?
>>>>>>>>>>>
>>>>>>>>>>> Thanks!
>>>>>>>>>>> Anne
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ___
>>>>>>>>>>> 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
>>>>>>>>
>>>>>>>
>>>>>>> Anne M. Hammond - Systems / Network Administration - Tech-X Corp
>>>>>>> hammond_at_txcorp.com 720-974-1840
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ___
>>>>>>> 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
>>>>>
>>>>
>>>> Anne M. Hammond - Systems / Network Administration - Tech-X Corp
>>>> hammond_at_txcorp.com 720-974-1840
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ___
>>>> users mailing list
>>>>
>>>> us...@open-mpi.org
>>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>
>>>
>>> --
>>> Jun.-Prof. Dr. Dominik Göddeke
>>> Hardware-orientierte Numerik für große Systeme
>>> Institut für Angewandte Mathematik (LS III)
>>> Fakultät für Mathematik, Technische Universität Dortmund
>>>
>>> http://www.mathematik.tu-dortmund.de/~goeddeke
>>>
>>> Tel. +49-(0)231-755-7218 Fax +49-(0)231-755-5933
>>> --
>>> Sent from my old-fashioned computer and not from a mobile device.
>>> I proudly boycott 24/7 availability.
>>>
>>>
>>> ___
>>> 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
>
> Anne M. Hammond - Systems / Network Administration - Tech-X Corp
> hammond_at_txcorp.com 720-974-1840
>
>
>
>
> ___
> 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/
> issue.
Note that this patch is on the OMPI SVN trunk. You can either build directly
from an SVN checkout or grab a nightly tarball here (get any r number >= 26862,
obviously, which will be tonight around 10pm US Eastern time at the earliest):
http://www.open-mpi.org/nightly/trunk/
-
t;,
>> ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
>> Can anybody confirm that the patch is good/correct? In particular
>> that the '__sun' part is the right thing to do?
>>
>> Thanks,
>>
>> Daniel
>>
>>
>>
>&g
r compiler flags in
the non-MPI install.
I also notice that you're not compiling the same .c files at all.
So if I'm understanding this thread right -- and I may well not be -- it seems
like you're saying:
- when I use gcc to compile main.c, the program runs file
- when I used mpicc to compile ../src/snd_0.1.c, the program fails
If that's the case, your comparing apples to oranges here.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ptions) and invoke the underlying gcc. Hence, mpicc is likely not your issue.
A bug (or set of bugs) in your MPI-based code is likely the issue. My best
advice to you is to use normal debugging techniques to find this(these) bug(s).
Good luck!
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
t devices, they can run Linux's raw
TCP/IP stack, too, not just the IPoIB stack).
Can you explain how you got your 5Gpbs and 12Gbps numbers? I'm already
suspicious of your testing methodology because 12Gpbs over a single RoCE port
just isn't possible... :-)
--
Jeff Squyres
[Our apologies if you receive multiple copies or if you are not related to MPI]
Dear MPI user,
The MPI Forum is about to ratify the MPI-3.0, a new version of the MPI standard.
As part of this process, we are soliciting feedback on the current draft
standard.
The draft document can be found here:
ortran_integer_t
#endif
-
Meaning that if someone else has defined MPI_Fint before us, we'll keep that
definition. Which actually seems like a bad idea, but even so, no one else
should be defining what MPI_Fint is.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal informa
seen this behavior?
>
> Best regards,
> Paul
> _______
> 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/
3.0 for, among other reasons, receiving messages
of unknown size. See http://blogs.cisco.com/performance/mpi-forum-roundup/ for
an explanation of MPROBE.
MPROBE, too, will be included in the upcoming OMPI v1.7 release.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
rchange the new handle types with legacy MPI code by accessing
the MPI_VAL member; it's the same old INTEGER handle that you're used to.
use mpi_f08
type(MPI_Comm) :: comm
integer :: old_style_comm_handle
comm = MPI_COMM_WORLD
old_style_comm_handle = comm
> Juan ESCOBAR
> Support MESONH
> Laboratoire d'Aérologie, O.M.P.
> 14 avenue Edouard Belin
> 31400 - TOULOUSE
> Tel : +33 (0)5-61-33-27-49
> Fax : +33 (0)5-61-33-27-90
>
> ___
> 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/
R
>>> Support MESONH
>>> Laboratoire d'Aérologie, O.M.P.
>>> 14 avenue Edouard Belin
>>> 31400 - TOULOUSE
>>> Tel : +33 (0)5-61-33-27-49
>>> Fax : +33 (0)5-61-33-27-90
>>>
>>> ___
>>> users mailing list
>>> us...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>
>
>
> --
> Juan ESCOBAR
> Support MESONH
> Laboratoire d'Aérologie, O.M.P.
> 14 avenue Edouard Belin
> 31400 - TOULOUSE
> Tel : +33 (0)5-61-33-27-49
> Fax : +33 (0)5-61-33-27-90
>
> ___
> 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/
r beyond 1.7/1.8. It's therefore "v1.9".
Make sense?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
n-MPI/CUDA feature will be only in the 1.9 serie or also on
> 1.7/1.8 ?
Good question.
Rolf -- do you plan to bring cuda stuff to v1.7.x?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
t;
>> You don't have permission to access / on this server.
>>
>> Apache Server at www.open-mpi.org Port 80
>
>
>
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/lis
___
>>> 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
> ___
> 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/
0_main_page.php).
On Aug 10, 2012, at 4:45 PM, Jeff Squyres wrote:
> I swear that there was an MPI-3 proposal for just about exactly this issue
> (because there is currently no MPI-standardized way to get this information).
>
> I honestly don't remember what happened to this pro
lots=16
shell$ mpirun --hostfile hostfile -np 4 --npernode 2 my_mpi_executable
# ^^ this runs a total of 4 MPI processes, 2 on each node
shell$ mpirun --hostfile hostfile -np 16 --npernode 8 my_mpi_executable
# ^^ this runs a total of 16 MPI processes, 8 on each node
-
...and so on.
--
expected a ";"
> {
> ^
>
> sjb_simple_smle_with_Rinside.cpp(35): warning #12: parsing restarts here
> after previous syntax error
> using namespace Rcpp;
> ^
>
> sjb_simple_smle_with_Rinside.cpp(77): error: identifier "as" is undefined
> const Map Xmat(as >(Xmat_sexp));
> ^
>
> sjb_simple_smle_with_Rinside.cpp(77): error: type name is not allowed
> const Map Xmat(as >(Xmat_sexp));
> ^
>
> sjb_simple_smle_with_Rinside.cpp(80): error: type name is not allowed
> const Map Ymat(as >(Ymat_sexp));
> ^
>
> sjb_simple_smle_with_Rinside.cpp(87): error: type name is not allowed
> const Map ua(as >(ua_sexp));
> ^
>
> sjb_simple_smle_with_Rinside.cpp(89): error: type name is not allowed
> const Map ub(as >(ub_sexp));
> ^
>
> sjb_simple_smle_with_Rinside.cpp(98): error: type name is not allowed
> const Map start_vector(as >(start_sexp));
> ^
>
> compilation aborted for sjb_simple_smle_with_Rinside.cpp (code 2)
>
>
> ___
> 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/
(MPI_COMM_WORLD);
>>
>> MPI_Group_rank(even_group, &even_rank);
>> MPI_Group_rank( odd_group, &odd_rank);
>> printf("%d %d %d\n",Iam, even_rank, odd_rank);
>>
>> MPI_Finalize(); /* let MPI finish up ... */
>> }
>>
>> ___
>> 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/
configure: failed program was:
> | program main
> |
> | end
> configure:28625: result: no
> configure:28639: error: Could not run a simple Fortran 77 program. Aborting.
>
> --
>
> System Software Overview:
>
> System Version: Mac OS X 10.7.4 (11E53)
> Kernel Version: Darwin 11.4.0
>
> Hardware Overview:
>
> Model Name: iMac
> Model Identifier: iMac12,1
> Processor Name: Intel Core i7
>
> --
>
> I hope I've provided the right/enough info, as I said I'm no whizz-kid at
> this stuff! I'd be glad of any help you can offer, please try and
> "dumb-it-down" for me!
>
> Thanks,
>
> Matt.
> ___
> 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/
(group, 1, 0 , &master);
> MPI_Group_excl(group, 1, 0, &workers);
> MPI_Comm_create(comm_world, master, &comm_master);
> MPI_Comm_create(comm_world, workers, &comm_workers);
> MPI_Finalize();
> }
>
> From: Jeff Squyres
> To: Open MPI Users
>
re may change a bit from the
old system to the new system. In Open MPI, you should be able to use "mpif77"
and/or "mpif90" to compile and link everything. No further MPI-related flags
are necessary (no need to -I to specify where mpif.h is located, no need to
-lmpi,
ally means a
mismatch between the tuples.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
MPI_Sendrecv(&x[ys[me]][xe[me]], 1, column_type, NeighBor[E], flag,
> > &x[ys[me]][xs[me]-1], 1, column_type, NeighBor[W], flag, comm2d, &status);
> >
> > /*Send my boundary to West and receive from Est*/
> > MPI_Sendrecv(&x[ys[me]][xs[me]], 1, column_type
>>
>>> "/opt/pgi/linux86-64/12.5/include/CC/stl/_threads.h", line 380: error:
>>> identifier "omp_unset_lock" is undefined
>>> omp_unset_lock(&_M_lock);
>>> ^
>>>
>>> 6 errors detected in the compilation of "vt_wrapper.cc".
>>> make: *** [vtwrapper-vt_wrapper.o] Error 2
>>> [root@rocks6staging vtwrapper]#
>>
>>
>>
>> --
>> Lloyd Brown
>> Systems Administrator
>> Fulton Supercomputing Lab
>> Brigham Young University
>> http://marylou.byu.edu
>> ___
>> 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/
ld be just warning if we can't register 3/4 of your physical
memory (we can't really test for anything more than that). But it doesn't
abort.
We could add a tunable that makes it abort in this case, if you think that
would be useful.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
t looks like
we're going to probably roll a 1.6.2 in the immediate future; we can include
this in there.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
I've merged the VT fix into the 1.6 branch; it will be available in tonight's
tarball.
Can you give a nightly v1.6 tarball a whirl to ensure it fixes your problem?
http://www.open-mpi.org/nightly/v1.6/
On Aug 23, 2012, at 7:30 PM, Jeff Squyres (jsquyres) wrote:
> Yes. VT
>>>
>>>>
>>>> ___
>>>> 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
>>
>>
>> ___
>> 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/
>>>>> mpirun noticed that the job aborted, but has no info as to the process
>>>>> that caused that situation.
>>>>> --
>>>>>
>>>>> Is there some
uot;, atomicity);
MPI_File is an opaque structure; you won't be able to access any of the fields
inside of it directly.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
> Thanking you in advance
>
> --
> Sudhir Kumar Sahoo
> Ph.D Scholar
> Dept. Of Chemistry
> IIT Kanpur-208016
> ___
> 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/
issue with this dataset from the
> symptoms that I can tell, but I wouldn't expect it to hang on
> khugepaged, or is this just a corner case?
It *could* be... but I really have no idea (haven't thought about huge page
support w.r.t. registered memory exhaustion / imbalance). Mellanox?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ost earlier
today:
http://www.open-mpi.org/community/lists/users/2012/08/20066.php
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
asked exactly the same question on both the Open MPI and MPICH2
lists at the same time -- know that our back-end data structures are different.
Hence, even if you could access the fields of Open MPI, that wouldn't help you
with MPICH2.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal i
Also, yes, if you installed libnuma after installing Open MPI, then you'll need
to re-build Open MPI. That being said, Open MPI 1.6 and beyond does not
require libnuma for process binding. It does need libnuma for memory binding,
though (hwloc uses libnuma behind the scenes for memor
45e47c in main ()
>
> Can anybody shed some light here on what could be wrong?
>
> Thanks,
>
> Yong Qin
> ___
> 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/
problem by providing some suggestions
> and clues.
>
> Thanking you very much.
>
> --
> WITH REGARDS
> M.L.N.Seshendra
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listi
gt; Memory:ef40-ef42
>
> loLink encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:143359307 errors:0 dropped:0 overruns:0
other hand we define the two-dimensional communicator
> using PERIODS = (/ .False., .True. /), we find
>
> PERIODS_X = F
> PERIODS_Y = F
>
> Your advice on the matter would be greatly appreciated.
>
> Regards,
>
> John.
>
> _______
his thread. That's why it creates a new thread in the web mail
archives. If you replied to the individual mails, they would thread properly
on the web mail archives.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
On Sep 7, 2012, at 5:58 AM, Jeff Squyres wrote:
> Also look for hardware errors. Perhaps you have some bad RAM somewhere. Is
> it always the same node that crashes? And so on.
Another thought on hardware errors... I actually have seen bad RAM cause
spontaneous reboots with no
ws build MPI
> problem. Since the simple code works on a Linux system with gfortran.
>
> Any ideas? I appreciate any response!
>
> Yonghui
>
> ___
> 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/
/include/string.h:78:34: error:
> 'restrict' has a previous declaration as 'const void* restrict'
> make[2]: *** [mpicxx.lo] Error 1
> make[2]: Leaving directory `.../openmpi-1.6.1-SunOS.sparc.64_gcc/ompi/mpi/cxx'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `.../openmpi-1.6.1-SunOS.sparc.64_gcc/ompi'
> make: *** [all-recursive] Error 1
> tyr openmpi-1.6.1-SunOS.sparc.64_gcc 127
>
>
> Has anyone else a similar problem? Is our system responsible for the
> problem so that I must open a service request or is something wrong
> with openmpi? Thank you very much for any help in advance.
>
>
> Kind regards
>
> Siegmar
>
> ___
> 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/
gt;
> Thanks.
>
> -Paul Edmon-
> _______
> 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;FILE* restrict'
>>> ...
>>>
>>> Many lines of similar errors.
>>>
>>> ...
>>> In file included from
>>> ../../../../openmpi-1.6.1/ompi/mpi/cxx/functions_inln.h:22:0,
>>> from ../../../../openmpi-1.6.1/ompi/mpi/cxx/mpicxx.h
;> I tried to change the address to 127.0.0.1 without luck. When I switch
>> from "automatic" to "manual" in the properties menue and start the
>> IP address with 127 a window pops up announcing that an IP address
>> starting with 127 is reserved for the loop
c/bin/rank_size
>>>>>>
>>>>>>
>>>>>> Is it a problem in the Open MPI implementation or in my rankfile?
>>>>>> How can I request which sockets and cores per socket are
>>>>>> available so that I can use correct
___
>>>>> users mailing list
>>>>> us...@open-mpi.org
>>>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>> ___
>>>> users mailing list
>>>> us...@open-mpi.org
>>
r" you mean someone compiling Open MPI?
>
> Yes
> ___
> 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 t
gt;>> /opt/mpi/openmpi-gnu4/lib64/libmpi.so.1(mca_pml_ob1_isend+0x4cb)
>>>>> [0x7fb58777509b]
>>>>> [limulus:04448] [14]
>>>>> /opt/mpi/openmpi-gnu4/lib64/libmpi.so.1(ompi_coll_tuned_bcast_intra_generic+0x37b)
>>>>> [0x7fb58770b55b]
>>>>> [limulus:04448] [15]
>>>>> /opt
George -- you're the owner of this part of the code. What do you want to do
here?
On Sep 12, 2012, at 12:37 PM, Brice Goglin wrote:
> Le 12/09/2012 17:57, Jeff Squyres a écrit :
>> Here's the r numbers with notable MX changes recently:
>>
>> https://svn.open-mp
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/
tell me what
>> exactly it is. Can anyone help me? thanks.
>>
>> Richard
>>
>>
>>
>>
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/list
..@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
>>
>>
>>
>> _________
gt; comm=0x627380)
> > at pallreduce.c:105
> > 105 err = comm->c_coll.coll_allreduce(sendbuf, recvbuf, count,
> >
> > It seems that there is a communication problem between some computers. But
> > the above series of test cannot tell me what
> > exactly
/community/help/
On Sep 25, 2012, at 11:54 AM, Jeff Squyres wrote:
> Hav you disabled firewalls on your nodes (e.g., iptables)?
>
> On Sep 25, 2012, at 11:08 AM, Richard wrote:
>
>> sometimes the following message jumped out when I run the ring program, but
>> not always
s, B failed to send message to C.
> I checked firewall config using chkconfig --list iptables on all the nodes.
> none of them are set as "on".
>
> Attached is all the information needed, my openmpi version is 1.6.1.
>
> thanks for your help.
> Richard
>
>
&g
On Sep 25, 2012, at 2:28 PM, Jeff Squyres wrote:
> mpirun --mca btl_if_exclude virbr0 ...
Gah; sorry, that should be:
mpirun --mca btl_tcp_if_exclude virbr0 ...
I forgot the "tcp" there in the middle.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information
_tcp_if_include bond0" because I know
> this is the high speed network interface I should use on each node.
Glad it works for you!
If you're not using those interfaces (they might be related to Xen, or
something like that?), you might want to disable them.
--
Jeff Squyres
jsquy.
__
> 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/
> [tyr.informatik.hs-fulda.de:23773] [[32457,0],0] ORTE_ERROR_LOG: Value out
>> of bounds in file
>>>> ../../../../openmpi-1.7a1r27358/orte/mca/odls/base/odls_base_default_fns.c
>> at line 1414
>>>>
>>>>
>>>>
>>>> tyr fd1
s/bogus /home/jsquyres/bogus2
% setenv OPAL_PREFIX /home/jsquyres/bogus2
% set path = (/home/jsquyres/bogus2/bin $path)
% mpirun -np 2 hostname
svbu-mpi027
svbu-mpi029
%
-
And it seems to work for me.
Are you doing something different?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal
fit your situation.
See http://www.open-mpi.org/faq/?category=running#mpirun-prefix for exactly
what this option does (and does not) do.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
r the runaround! I'm going to blame it on jet lag. :-)
On Sep 26, 2012, at 3:06 AM, Richard wrote:
> Jeff,
>
> It was a typo in my last post, I did use "--mca btl_tcp_if_exclude virbr0"
> and it did not work.
>
> At 2012-09-25 21:10:24,"Jeff Squyres&q
" prior to termination.
>>>>>>>>>>
>>>>>>>>>> 2. this process called "init", but exited without calling "finalize".
>>>>>>>>>> By rule, all processes that call "init" MUST call &q
al Research,
> National Institute for Environmental Studies,
> 16-2 Onogawa, Tsukuba, Ibaraki, 305-8506 Japan
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy.
itialization
> is very fast and the hacked TSD problem does not cause segfault. Only
> the perfomance loss could be induced. The reason is a very long story,
> please let it omitted today.
>
> Best 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/
ould be fine.
> 2. Can I create my own communicator and set its MPI_TAG_UB to whatever I want
> ?
As Hristo said, no. It's a limit in Open MPI.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
get:
>>>
>>> [cp2558][[30209,1],0][connect/btl_openib_connect_oob.c:490:qp_create_o
>>> ne] error creating qp errno says Cannot allocate memory
>>>
>>> With Open-MPI 1.5.4, the upper bound is 17438272 (at least in our build).
>>> That expla
riables, right ?
It's not a variable that's the issue. If you do a receive for tag -3 and OMPI
sends an internal control message with tag -3, you might receive it instead of
OMPI's core. And that would be Bad.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
901 - 1000 of 4070 matches
Mail list logo
