That's really helpful, thanks!
2009/1/8 Jeff Squyres
> I created 3 wiki pages over the holidays:
>
> * https://svn.open-mpi.org/trac/ompi/wiki/devel/CreateComponent
> How to add a new to / remove an old component from Open MPI
> * https://svn.open-mpi.org/trac/ompi/wiki/devel/CreateFramework
Hello
I'm in the midst of writing a BTL component, all is going well although
today I ran into something unexpected. In the
mca_btl_base_module_add_procs_fn_t function, I'm trying to call
mca_oob_tcp_send_nb() which is returning -12 (ORTE_ERR_UNREACH). Is this
normal or have I done something wrong
d a buffer instead of an iovec, then the call
> would be to orte_rml.send_buffer_nb.
>
> Ralph
>
>
>
> On Jan 19, 2009, at 1:01 PM, Timothy Hayes wrote:
>
> Hello
>>
>> I'm in the midst of writing a BTL component, all is going well although
>> tod
Hi everyone,
I'm currently writing my own BTL component that utilises a lightweight Linux
socket module. It wouldn't have nearly as much functionality as a TCP/IP
socket but it does the job and I managed to add a simple polling function
into the module, it sleeps for whatever amount of time is en
Hello,
I'm working on an OpenMPI BTL component and am having a recurring problem, I
was wondering if anyone could shed some light on it. I have a component
that's quite straight forward, it uses a pair of lightweight sockets to take
advantage of being in a virtualised environment (specifically Xen
o deal with
> the cases where a fragment cannot be allocated. We changed most of the BTLs
> to use _get instead of _wait few months ago.
>
> Thanks,
>george.
>
>
> On Mar 23, 2009, at 11:58 , Timothy Hayes wrote:
>
> Hello,
>>
>> I'm working on an
became available only when returned by
>>> the BTL, this can lead to deadlocks in some cases. The workaround is to ban
>>> the usage of the blocking _wait function, and replace it with the
>>> non-blocking version _get. The PML has all the required logic to deal with
>>
Do you mean the code in OPAL/event? If so, it's a customised libevent. I've
seen it used in OpenMPI to poll/select open sockets, it allows the
programmer register their own callback functions for when this happens. Just
ignore me if this wasn't what you were asking about though :-)
Tim
2009/4/3 E
I was wondering if someone might be able to shed some light on a couple of
questions I have.
When you receive a fragment/base_descriptor in a BTL module, is the raw data
allowed to be fragmented when you invoke the callback function? By that I
mean, I'm using a circular buffer in each endpoint so
Apr 12, 2009, at 21:58 , Timothy Hayes wrote:
>
> I was wondering if someone might be able to shed some light on a couple of
>> questions I have.
>>
>> When you receive a fragment/base_descriptor in a BTL module, is the raw
>> data allowed to be fragmented when you i
>From what I understand MPI_Send will hit 3 separate layers of code before
reaching the socket file descriptors you've found. The PML (Point to Point
Messaging Layer) is a layer that bridges the MPI semantics from the
underlying point to point communications. The standard PML implementation is
call
I uploaded it to http://www.hotshare.net/file/131218-829472246c.html
I'm not sure if it's any good or even if it's 100% accurate; but if someone
gets any use out of it, that would be good.
Tim
2009/4/17 Jeff Squyres
> On Apr 16, 2009, at 11:38 AM, Timothy Hayes wrot
Are you talking about my document? If so, that's no problem at all. If there
are any mistakes in my facts just let me know and I'll change them.
Tim
2009/5/6 Jeff Squyres
> Thanks!
>
> Would you mind if I posted this on www.open-mpi.org?
>
>
>
> On Apr 25, 2
Would this be okay?
@misc{hayes09_ugrad_xenmpi,
author = {Timothy Hayes},
title = {An Effcient Open MPI Transport System for Virtual Worker Nodes},
howpublished = {Trinity College Dublin Final Year Project},
year = {2009},
note = "Undergraduate Dissertation",
}
It'
Is it not a forward definition and then defined in the PML components
individually based on their own requirements?
2009/12/7 Pavel Shamis (Pasha)
> In the ompi_proc_t structure (ompi/proc/proc.h:54) we keep pointer to
> proc_pml - "struct mca_pml_base_endpoint_t* proc_pml" . I tired to find
> d
Sorry, I think I read your question too quickly. Ignore me. :-)
2009/12/7 Timothy Hayes
> Is it not a forward definition and then defined in the PML components
> individually based on their own requirements?
>
> 2009/12/7 Pavel Shamis (Pasha)
>
> In the ompi_proc_t structure
If I understood your question correctly, it's not really the MPI
implementation's duty to solve this issue. You either have to copy the
binaries to each machine manually or (more usually) each machine is given
access to a common shared file system.
Tim
On 22 March 2010 15:42, herbey zepeda wrote
Hello everyone,
I'm a regular OpenMPI user but I'm new to the strange world of development
and hence this mailing list. I'm currently working on a project that
involves OpenMPI and I was wondering if I might get some guidance and
pointers in the right direction.
In brief, my project is trying to m
Hi everyone,
Thank you all for your replies. I've now read those additional papers and
went through the slides of the Open MPI workshop. I'm still a bit hazy on
the architecture of Open MPI (especially relevant to my project) so what
I've done is written what I think I understand about process to
19 matches
Mail list logo
