It appears I cannot build the trunk on Mac - I hit this issue when I updated
from the trunk and rebuilt from autogen this evening:
make[7]: *** No rule to make target `vt_filthandler.cc', needed by
`vtfilter-vt_filthandler.o'. Stop.
Vanilla configure - I didn't turn VT off like I usually do.
That's still not quite right, per OMPI conventions.
If you don't find it, you shouldn't warn, you should have some other
AC_MSG_CHECKING and then indicate that that particular check failed.
E.g.
AC_MSG_CHECKING([if can use dynamic SL support])
AS_IF([test "$1_have_dynamic_sl" = "1"],
Hi,
As I advanced in my implementation of TIPC BTL, I added the component
and tried to run hello_c program to test.
Then I got this segmentation fault. It seemed happening after the call
"mca_btl_tipc_add_procs".
The error message displayed:
[oak:23192] *** Process received signal ***
Hi Jeff,
> > First, we created a new BTL component, 'tofu BTL'. It's not so special
> > one but dedicated to our Tofu interconnect. But its latency was not
> > enough for us.
> >
> > So we created a new framework, 'LLP', and its component, 'tofu LLP'.
> > It bypasses request object creation in
On Jun 29, 2011, at 3:57 AM, Kawashima wrote:
> First, we created a new BTL component, 'tofu BTL'. It's not so special
> one but dedicated to our Tofu interconnect. But its latency was not
> enough for us.
>
> So we created a new framework, 'LLP', and its component, 'tofu LLP'.
> It bypasses
Hi Sylvain,
> > Also, we modified tuned COLL to implement interconnect-and-topology-
> > specific bcast/allgather/alltoall/allreduce algorithm. These algorithm
> > implementations also bypass PML/BML/BTL to eliminate protocol and
> software
> > overhead.
> This seems perfectly valid to me. The
Kawashima-san,
Congratulations for your machine, this is a stunning achievement !
> Kawashima wrote :
> Also, we modified tuned COLL to implement interconnect-and-topology-
> specific bcast/allgather/alltoall/allreduce algorithm. These algorithm
> implementations
Hi Jeff, Ralph, and all,
Thank you for your reply.
RIKEN and Fujitsu will work toword 10Pflops with Open MPI continuously.
Here we can explain some parts of our MPI:
As page 13 of Koh Hotta's presentation shows, we extended OMPI
communication layers.
>