alex -> alex-ma
alinas -> alinask
amikheev -> alex-mikheev
vasily -> vasilyMellanox
On Wed, Sep 10, 2014 at 1:46 PM, Jeff Squyres (jsquyres) wrote:
> As the next step of the planned migration to Github, I need to know:
>
> - Your Github ID (so that you can be added to
Thanks jeff, I'll make it work.
I'm moving my apartment tomorrow, so I hope I'll get to it on the weekend.
On 28 Apr 2014 18:09, "Jeff Squyres (jsquyres)" wrote:
> If it helps, I just updated that to the most recent OMPI trunk SVN
> revision. There were at least 3 files
I'm the original developer. The patch never got merged, but I have patches
to some branches. Which version are you using?
On 24 Apr 2014 19:07, "Pavel V. Kaygorodov" wrote:
> Hi!
>
> What is current status of mosix support in OpenMPI?
> I have tried patches from
>
Hi,
I'm having trouble getting the OPAL_OUTPUT to print. I'm trying the
following command line (with no success):
`pwd`/osh_install/bin/oshrun --map-by node -np 2 -mca orte_debug true -mca
orte_debug_verbose 100 -mca orte_report_silent_errors true -mca
orte_map_stddiag_to_stderr true
/lab/mosix/alexam02/ompi-jeff/opal'
make: *** [all-recursive] Error 1
Should this be a trac ticket?
Alex
On Fri, Sep 6, 2013 at 1:22 PM, Alex Margolin <alex.margo...@mail.huji.ac.il
> wrote:
> Hi,
>
> I'm building ompi r29104 with the following command:
>
> make dist
Hi,
I'm building ompi r29104 with the following command:
make distclean && ./autogen.sh && ./configure
--prefix=/cs/mosna/alexam02/ompi CFLAGS=-m64 CXXFLAGS=-m64 --without-hwloc
--disable-mpi-threads --disable-progress-threads
--enable-mca-no-build=maffinity,paffinity
Hi,
I'm not sure if anyone remembers, but I was working on Open MPI support
for MOSIX in the form of several MCA modules (turned out to be BTL,
ODLS, and RAS). It's pretty much finished now, thanks to your help (I
got many useful tips and clarifications from this mailing list). As I
said
On 04/25/2012 02:57 PM, Ralph Castain wrote:
Strange that your code didn't generate any symbols - is that a mosix thing?
Have you tried just adding opal_output (so it goes to a special diagnostic
output channel) statements in your code to see where the segfault is occurring?
It looks like you
Hi,
I'm writing a new polling module and I stumbled upon some strange code:
The following function is implemented in
openmpi-trunk/opal/mca/event/libevent2013/libevent/signal.c :
evsig_add(struct event_base *base, evutil_socket_t evsignal, short old,
short events, void *p)
- It appears the
On 04/15/2012 12:36 AM, Ralph Castain wrote:
The 1.6 branch is a stable series - no new features will be added to it, so
your patch won't be going there. I'd focus solely on the trunk.
- Can I add my module(s) to 1.5 branch? (as well as the trunk?)
What you're doing with he RAS is fine for
On 04/15/2012 12:36 AM, Ralph Castain wrote:
The 1.6 branch is a stable series - no new features will be added to it, so
your patch won't be going there. I'd focus solely on the trunk.
OK, but what would you recommend for benchmarking? a local 1.6 checkout?
What you're doing with he RAS is
be launching at the same time!
On Apr 13, 2012, at 10:07 AM, Alex Margolin wrote:
Hi,
The next component I'm writing is a component for allocating nodes to
run the processes of an MPI job.
Suppose I have a "getbestnode" executable which not only tells me the
best location for spawning a n
Hi,
The next component I'm writing is a component for allocating nodes to
run the processes of an MPI job.
Suppose I have a "getbestnode" executable which not only tells me the
best location for spawning a new process,
but it also reserves the space (for some time), so that every time I run
it I
Hi,
As I'm working out the bugs in my component I used TCP as reference and
came across the following:
In mca_btl_tcp_alloc (openmpi-trunk/ompi/mca/btl/tcp/btl_tcp.c:188) the
first segment is initialized to point to "frag + 1".
I don't get it... how/when is this location allocated? Isn't it
lt; local module */
};
typedef struct mca_btl_mosix_component_t mca_btl_mosix_component_t;
You can then overload that component with your additional info, leaving the
base component to contain the required minimal elements.
On Apr 1, 2012, at 1:59 AM, Alex Margolin wrote:
I traced t
with the way I initialize my component -
I'll resume debugging after lunch.
Alex
On 03/31/2012 07:04 PM, Alex Margolin wrote:
P.S. I get the following Error - I'm pretty sure my BTL is to blame here:
alex@singularity:~/huji/benchmarks/simple$ mpirun -mca
btl_base_verbose 100 -mca btl self,mos
on the TCP side. Still, UDP may perform
better with fire-and-forget scenarios.
Thanks a lot (and sorry for the hassle),
Alex
On 03/31/2012 07:04 PM, Alex Margolin wrote:
Hi,
I think i'm close to finishing an initial version of the MOSIX support
for open-mpi. A perliminary draft is attached
Hi,
I think i'm close to finishing an initial version of the MOSIX support
for open-mpi. A perliminary draft is attached.
The support consists of two modules: ODLS module for launching processes
under MOSIX, and BTL module for efficient communication between processes.
I'm not quite there yet
have to implement. The RMA protocols (GET or PUT)
are optional, and are specified by setting specific bits in your BTL flag.
Regarding the TCP BTL, the two RMA operations are "fake", they are simply
implemented on top of mca_btl_tcp_endpoint_send.
george.
On Mar 17, 2012, at 18
e upper layer
of a message, but this is only for MCA_BTL_TCP_HDR_TYPE_SEND.
What about MCA_BTL_TCP_HDR_TYPE_PUT?
Thanks,
Alex
On 03/04/2012 02:54 AM, George Bosilca wrote:
On Mar 3, 2012, at 18:18 , Alex Margolin wrote:
I've figured that what I really need is to write my own BTL component, rather
't start without any (so I had to turn it back on). Could
you tell me if there is a way to run the application without making any
mmap() calls with MAP_SHARED? Currently, mosrun is run with -w asking it
to fail (return -1) on any such system-call.
Thanks for your help,
Alex
On Mar 17, 20
Hi,
I want to launch Open-MPI processes using another process: instead of
using "hello" x 4 I want to run "mosrun -w hello" x 4 when I start it
with "mpirun -n 4 hello". I've cloned the "default" component in
orte/mca/odls (from trunk) - see patch attached.
I'm getting an error which is
Hi,
I'm implementing a new BTL component, and
1. I read the TCP code and ran into the three fragment lists:
/* free list of fragment descriptors */
ompi_free_list_t tcp_frag_eager;
ompi_free_list_t tcp_frag_max;
ompi_free_list_t tcp_frag_user;
I've looked it up, and found that
te frequently. It's how BTL's
like openib progress their outstanding message passing.
On Mar 2, 2012, at 2:22 PM, Alex Margolin wrote:
On 03/02/2012 04:33 PM, Jeffrey Squyres wrote:
Note that the OMPI 1.4.x series is about to be retired. If you're doing new
stuff, I'd advise you to be worki
On 03/02/2012 04:33 PM, Jeffrey Squyres wrote:
Note that the OMPI 1.4.x series is about to be retired. If you're doing new
stuff, I'd advise you to be working with the Open MPI SVN trunk. In the trunk,
we've changed how we build libevent, so if you're adding to it, you probably
want to be
/x86_64-linux-gnu/libpthread.so.0(+0x10060)
[0x7f7d6ac26060]
[singularity:32552] *** End of error message ***
Segmentation fault
alex@singularity:~/huji/benchmarks/simple$
Any ideas?
On 03/02/2012 01:26 PM, Alex Margolin wrote:
Hi,
I'm trying to replace the poll() function with mine (say poll2
Hi,
I'm trying to replace the poll() function with mine (say poll2() in
poll2.c), and I got some building errors.
This is after I copied poll2.c into opal/events/ and added it in the
sources list in Makefile.am in that folder.
...
Making all in tools/wrappers
make[2]: Entering directory
Hi,
I'm developing a new module under for BTL component to utilize an
existing distributed computing software in our lab.
I decided to write a TCP-like interface (implementing socket(),
connect(), accept(), send(), recv(), etc.) and then copy and modify
the existing BTL TCP module to create my
28 matches
Mail list logo