Re: [OMPI users] latest Intel CPU bug

nned here, Power and Sparc too) are vulnerable to >> some bugs. >> >> >> Full disclosure, i have no affiliation with Intel, but i am getting >> pissed with the hysteria around this issue. >> >> Gilles >> >> >> On 1/5/2018 3:54 PM, John Chludzi

Re: [OMPI users] latest Intel CPU bug

ck market tips > for Hacker News and Twitter? > > Thanks, > > Jeff > > On Thu, Jan 4, 2018 at 3:53 PM, John Chludzinski gmail.com> wrote: > >> From https://semiaccurate.com/2018/01/04/kaiser-security- >> holes-will-devastate-intels-marketshare/ >> >>

Re: [OMPI users] latest Intel CPU bug

From https://semiaccurate.com/2018/01/04/kaiser-security-holes-will-devastate-intels-marketshare/ Kaiser security holes will devastate Intel’s marketshareAnalysis: This one tips the balance toward AMD in a big wayJan 4, 2018 by Charlie Demerjian This l

Re: [OMPI users] Message queue in MPI?

I assume there are setting for this? On Thu, May 2, 2013 at 3:23 PM, John Chludzinski wrote: > If I'm using MPI_Send(...) and MPI_Recv(...) in a producer/consumer > model and choose not to buffer messages internally (in the app), > allowing them to acumulate in the MPI layer, h

[OMPI users] Message queue in MPI?

If I'm using MPI_Send(...) and MPI_Recv(...) in a producer/consumer model and choose not to buffer messages internally (in the app), allowing them to acumulate in the MPI layer, how large of an MPI message queue can I expect before something breaks? ---John

Re: [OMPI users] MPI based HLA/RTI ?

Mainly responding to Ralph's comments. In HLA a federate (MPI process) can join and leave a federation (MPI collective) independently from other federates. And rejoin later. ---John On Mon, Apr 22, 2013 at 11:20 AM, George Bosilca wrote: > On Apr 19, 2013, at 17:00 , John Chl

Re: [OMPI users] MPI based HLA/RTI ?

> > > > On Apr 16, 2013, at 3:20 AM, George Bosilca wrote: > > There is an ongoing effort to address the potential volatility of > processes in MPI called ULFM. There is a working version available at > http://fault-tolerance.org. It supports TCP, sm and IB (mostly). You will

Re: [OMPI users] MPI based HLA/RTI ?

Is that "in the works"? On Mon, Apr 15, 2013 at 11:33 AM, Ralph Castain wrote: > > On Apr 15, 2013, at 8:29 AM, John Chludzinski > wrote: > > That would seem to preclude its use for an RTI. Unless you have a card up > your sleeve? > > > One can relax tho

Re: [OMPI users] MPI based HLA/RTI ?

t it allows programs to > come/go at will - i.e., not every program has to start at the same time, > nor complete at the same time. MPI requires that all programs be executing > at the beginning, and that all call finalize prior to anyone exiting. > > > On Apr 15, 2013, at 8:14 AM, Joh

Re: [OMPI users] MPI based HLA/RTI ?

would support send/recv (i.e., MPI-1), but not > collectives, and so would allow communication between arbitrary programs. > > Not specifically targeting HLA/RTI, though I suppose a wrapper that > conformed to that standard could be created. > > On Apr 15, 2013, at 7:50 AM, J

Re: [OMPI users] MPI based HLA/RTI ?

on between LPs (federates in HLA). But these LPs are usually the same program. ---John On Mon, Apr 15, 2013 at 10:22 AM, John Chludzinski wrote: > Is anyone aware of an MPI based HLA/RTI (DoD High Level Architecture > (HLA) / Runtime Infrastructure)? > > ---John

[OMPI users] MPI based HLA/RTI ?

Is anyone aware of an MPI based HLA/RTI (DoD High Level Architecture (HLA) / Runtime Infrastructure)? ---John

Re: [OMPI users] client-server example

Client sending message 2 > Client sending message 3 > Client sending message 4 > Client sending message 5 > $ > > > > > On Apr 13, 2013, at 7:24 PM, John Chludzinski > wrote: > >> Yep, I saw both semi-colons but the client process hangs at: >> >> M

Re: [OMPI users] client-server example

t; be protected from the shell. I would just put quotes around the whole thing. > > Other than that, it looks okay to me...I assume you are using a 1.6 series > release? > > On Apr 13, 2013, at 4:54 PM, John Chludzinski > wrote: > >> After I replaced ";" wi

Re: [OMPI users] client-server example

aused that situation. -- [jski:02429] [[59675,0],0] -> [[59187,0],0] (node: jski) oob-tcp: Number of attempts to create TCP connection has been exceeded. Cannot communicate with peer. On Sat, Apr 13, 2013 at 7:24 PM, John Chludzinski wrote: > Sorry: The prev

Re: [OMPI users] client-server example

or to exiting or it will be considered an "abnormal termination" On Sat, Apr 13, 2013 at 7:16 PM, John Chludzinski wrote: > After I "source mpi.ksk", PATH is unchanged but LD_LIBRARY_PATH is there: > >$ print $LD_LIBRARY_PATH >/usr/lib64/openmpi/lib/ > >

Re: [OMPI users] client-server example

rinted - just copy/paste > the line below "server available at". > > On Apr 12, 2013, at 10:58 PM, John Chludzinski > wrote: > >> Found the following client-server example (code) on >> http://www.mpi-forum.org and I'm trying to get it to work. Not sure >

[OMPI users] client-server example

Found the following client-server example (code) on http://www.mpi-forum.org and I'm trying to get it to work. Not sure what argv[1] should be for the client? The output from the server side is: server available at 4094230528.0;tcp://192.168.1.4:55803+4094230529.0;tcp://192.168.1.4:51618:

Re: [OMPI users] Newbie question?

ssage that you are getting could be because of this. As a > consequence, if you have a RDMA supported device, you might be getting poor > performance. > > A wealth of information is available in the FAQ section regarding these > things. > > -- > Sent from my iPhone > > On Se

Re: [OMPI users] Newbie question?

ed and only > one context is specified (arg0 is the parameter > name; arg1 is the parameter value) > > Could you explain the args: btl and ^openib ? > > ---John > > > On Sun, Sep 16, 2012 at 12:26 AM, John Chludzinski < > john.chludzin.

Re: [OMPI users] Newbie question?

explain the args: btl and ^openib ? ---John On Sun, Sep 16, 2012 at 12:26 AM, John Chludzinski < john.chludzin...@gmail.com> wrote: > BINGO! That did it. Thanks. ---John > > > On Sat, Sep 15, 2012 at 9:32 PM, Ralph Castain wrote: > >> No - the mca param has to

Re: [OMPI users] Newbie question?

processes have sent help message > help-mpi-btl-base.txt / btl:no-nics > [elzbieta:02374] Set MCA parameter "orte_base_help_aggregate" to 0 to see > all help / error messages > > > On Sat, Sep 15, 2012 at 8:22 PM, Ralph Castain wrote: > >> Try adding "

Re: [OMPI users] Newbie question?

Try adding "-mca btl ^openib" to your cmd line and see if that cleans it > up. > > > On Sep 15, 2012, at 12:44 PM, John Chludzinski > wrote: > > There was a bug in the code. So now I get this, which is correct but how > do I get rid of all these ABI, CMA, etc.

Re: [OMPI users] Newbie question?

rror messages On Sat, Sep 15, 2012 at 3:34 PM, John Chludzinski < john.chludzin...@gmail.com> wrote: > BTW, here the example code: > > program scatter > include 'mpif.h' > > integer, parameter :: SIZE=4 > integer :: numtasks, rank, sendcount, recvcount, sour

Re: [OMPI users] Newbie question?

rocessors. Terminating.' endif call MPI_FINALIZE(ierr) end program On Sat, Sep 15, 2012 at 3:02 PM, John Chludzinski < john.chludzin...@gmail.com> wrote: > # export LD_LIBRARY_PATH > > > # mpiexec -n 1 printenv | grep PATH > LD_LIBRARY_PATH=/usr/lib/openmpi/lib/ > &

Re: [OMPI users] Newbie question?

> Ah - note that there is no LD_LIBRARY_PATH in the environment. That's the > problem > > On Sep 15, 2012, at 11:19 AM, John Chludzinski > wrote: > > $ which mpiexec > /usr/lib/openmpi/bin/mpiexec > > # mpiexec -n 1 printenv | grep PATH > > PATH=/usr/lib

Re: [OMPI users] Newbie question?

xec -n 1 printenv | > grep PATH". Sometimes the ld_library_path doesn't carry over like you think > it should > > > On Sep 15, 2012, at 10:00 AM, John Chludzinski > wrote: > > I installed OpenMPI (I have a simple dual core AMD notebook with Fedora > 16) via: >

[OMPI users] Newbie question?

I installed OpenMPI (I have a simple dual core AMD notebook with Fedora 16) via: # yum install openmpi # yum install openmpi-devel # mpirun --version mpirun (Open MPI) 1.5.4 I added: $ PATH=PATH=/usr/lib/openmpi/bin/:$PATH $ LD_LIBRARY_PATH=/usr/lib/openmpi/lib/ Then: $ mpif90 ex1.f95 $ mpiexe