I'm about ready to start on the connection modularity stuff in the
openib BTL. A few changes are getting rolled up in this work:
1. Modularize the connection scheme in the openib BTL as per previous
discussions (use function pointers to choose between the current OOB
wireup and the RDMA
Aurelien Bouteiller wrote:
Hi Ralph and everyone,
I just want to make sure the proposed usecases does not break one of the
current open MPI feature I require. For FT purposes, I need to get some
specific hosts (lets say with a better MTBF). Those hosts are not part
of the MPI_COMM_WORLD but
On Thu, Jul 26, 2007 at 04:29:40PM +0300, Gleb Natapov wrote:
> On Thu, Jul 26, 2007 at 09:12:26AM -0400, Jeff Squyres wrote:
> > I got a problem in MTT runs last night with the openib BTL w.r.t.
> > credits:
> >
> > [...lots of IMB output...]
> > #bytes #repetitions t_min[usec]
On 7/25/07, Jeff Squyres wrote:
Be sure to read this thread in order -- the conclusion of the thread
was that we now actually *do* return NULL, per POSIX advice.
OK, I got confused. And now, MPI_Free_mem is going to fail with a NULL
pointer? Not sure what POSIX says, but
On Jul 26, 2007, at 12:42 PM, Lisandro Dalcin wrote:
Be sure to read this thread in order -- the conclusion of the thread
was that we now actually *do* return NULL, per POSIX advice.
OK, I got confused. And now, MPI_Free_mem is going to fail with a NULL
pointer? Not sure what POSIX says, but
Mohamad -
A couple of comments / questions:
1) Why do you need the #if OMPI_GROUP_SPARSE in communicator/comm.c?
That seems like
part of the API that should under no conditions change based on
sparse/not sparse
2) I think it would be better to always have the flags and macros
On Thu, July 26, 2007 12:20 pm, Brian Barrett wrote:
> Mohamad -
>
> A couple of comments / questions:
>
> 1) Why do you need the #if OMPI_GROUP_SPARSE in communicator/comm.c?
> That seems like
> part of the API that should under no conditions change based on
> sparse/not sparse
>
I don't,
On Jul 26, 2007, at 12:00 PM, Mohamad Chaarawi wrote:
2) I think it would be better to always have the flags and macros
available (like OMPI_GROUP_SPORADIC and OMPI_GROUP_IS_SPORADIC) even
when sparse groups are disabled. They dont' take up any space, and
mean less #ifs in the general code
Hi Aurelien
Perhaps some bad news on this subject - see below.
On 7/26/07 7:53 AM, "Ralph H Castain" wrote:
>
>
>
> On 7/26/07 7:33 AM, "rolf.vandeva...@sun.com"
> wrote:
>
>> Aurelien Bouteiller wrote:
>>> Currently I proceed to two different
On Thu, July 26, 2007 1:18 pm, Brian Barrett wrote:
> On Jul 26, 2007, at 12:00 PM, Mohamad Chaarawi wrote:
>
>>> 2) I think it would be better to always have the flags and macros
>>> available (like OMPI_GROUP_SPORADIC and OMPI_GROUP_IS_SPORADIC) even
>>> when sparse groups are disabled. They
On Jul 26, 2007, at 1:01 PM, Mohamad Chaarawi wrote:
On Thu, July 26, 2007 1:18 pm, Brian Barrett wrote:
On Jul 26, 2007, at 12:00 PM, Mohamad Chaarawi wrote:
2) I think it would be better to always have the flags and macros
available (like OMPI_GROUP_SPORADIC and OMPI_GROUP_IS_SPORADIC)
On Thu, July 26, 2007 2:07 pm, Brian Barrett wrote:
> On Jul 26, 2007, at 1:01 PM, Mohamad Chaarawi wrote:
>
>>
>> On Thu, July 26, 2007 1:18 pm, Brian Barrett wrote:
>>> On Jul 26, 2007, at 12:00 PM, Mohamad Chaarawi wrote:
>>>
> 2) I think it would be better to always have the flags and
Ralph H Castain wrote:
After some investigation, I'm afraid that I have to report that this - as
far as I understand what you are doing - may no longer work in Open MPI in
the future (and I'm pretty sure isn't working in the trunk today except
[maybe] in the special case of hostfile - haven't
On 7/26/07 2:24 PM, "Aurelien Bouteiller" wrote:
> Ralph H Castain wrote:
>> After some investigation, I'm afraid that I have to report that this - as
>> far as I understand what you are doing - may no longer work in Open MPI in
>> the future (and I'm pretty sure isn't
mpirun -hostfile big_pool -n 10 -host 1,2,3,4 application : -n 2 -host
99,100 ft_server
This will not work: this is a way to launch MIMD jobs, that share the
same COMM_WORLD. Not the way to launch two different applications that
interact trough Accept/Connect.
Direct consequence on simple
15 matches
Mail list logo