I'm trying to figure out if MPI is a general enough message passing protocol that you could implement BEEP over it, and whether it would be a good idea. In particular, whether MPI could be faster than TCP. Any pointers or thoughts would be greatly appreciated. Thanks, Sam
> I'm trying to figure out if MPI is a general enough message passing > protocol that you could implement BEEP over it, and whether it would > be a good idea. In particular, whether MPI could be faster than TCP. > > Any pointers or thoughts would be greatly appreciated. MPI = http://www-unix.mcs.anl.gov/mpi/standard.html ??? or something else? /mtr
Quoting mrose <at> dbc.mtview.ca.us, on Sun, Apr 09, 2006 at 09:10:41AM -0700: > >I'm trying to figure out if MPI is a general enough message passing > >protocol that you could implement BEEP over it, and whether it would > >be a good idea. In particular, whether MPI could be faster than TCP. > > > >Any pointers or thoughts would be greatly appreciated. > > MPI = http://www-unix.mcs.anl.gov/mpi/standard.html ??? or something > else? Sorry, yes, that MPI. Sam
Marshall Rose wrote: >> I'm trying to figure out if MPI is a general enough message passing >> protocol that you could implement BEEP over it, and whether it would >> be a good idea. In particular, whether MPI could be faster than TCP. >> >> Any pointers or thoughts would be greatly appreciated. > > > MPI = http://www-unix.mcs.anl.gov/mpi/standard.html ??? or something > else? > Very odd thought. MPI is used widely as a message-passing API (particularly w/ C,C++ and Fortran) for high performance computing HPC). The synchronous (2-way) MPI is used much more widely than the 1-way (remote memory read/write) enabled version. It supports user-space synchronous message-passing. (There is also support, using immediate/nonblocking mode for asynchronous messaging.) The bulk of MPI is oriented towards supporting collective operations (e.g. all reduce) over a group of such processes participating in point to point interactions with each other (grouped together in a communicator). Not sure this is particularly relevant for BEEP. Why would you want to do this? Perhaps what you might be after is that often HPC clusters are built over extremely high-performance interconnects that are non-IP-based. For instance, ARMCI and LAPI, based on infiniband/quadrics/myrinet/IBM Federation switches and other network I/O cards(Continue reading)
Quoting vijay <at> saraswat.org, on Sun, Apr 09, 2006 at 02:24:59PM -0400: > Marshall Rose wrote: > > >>I'm trying to figure out if MPI is a general enough message passing > >>protocol that you could implement BEEP over it, and whether it would > >>be a good idea. In particular, whether MPI could be faster than TCP. > >> > >>Any pointers or thoughts would be greatly appreciated. > > > > > >MPI = http://www-unix.mcs.anl.gov/mpi/standard.html ??? or something > >else? > > > Very odd thought. > > MPI is used widely as a message-passing API (particularly w/ C,C++ and > Fortran) for high performance computing HPC). The synchronous (2-way) > MPI is used much more widely than the 1-way (remote memory read/write) > enabled version. It supports user-space synchronous message-passing. > (There is also support, using immediate/nonblocking mode for > asynchronous messaging.) The bulk of MPI is oriented towards supporting > collective operations (e.g. all reduce) over a group of such processes > participating in point to point interactions with each other (grouped > together in a communicator). Not sure this is particularly relevant for > BEEP. > Why would you want to do this? Perhaps what you might be after is that > often HPC clusters are built over extremely high-performance > interconnects that are non-IP-based. For instance, ARMCI and LAPI, based > on infiniband/quadrics/myrinet/IBM Federation switches and other(Continue reading)
###########################################
## Vortex Library 0.8.11 Stable Release ##
###########################################
Release note
~~~~~~~~~~~~
Advanced Software Production Line is proud to announce the Vortex
Library 0.8.11 availability: an open source "BEEP Core" protocol
implementation written in C, mapped onto TCP/IP.
Vortex Library has been developed inside the Af-Arch project as its
data transport layer.
Vortex Library is a stable and robust application protocol
development toolkit. Currently it is running under Microsoft Windows
and GNU/Linux platforms.
Check out the following links to get ready with Vortex Library:
- http://vortex.aspl.es
[Vortex Library homepage]
- http://www.sf.net/projects/vortexlibrary
[Sources and Win32 binaries]
- http://fact.aspl.es
[Af-Arch homepage where Vortex Library is being developed]
- http://www.beepcore.org
(Continue reading)
> Advanced Software Production Line is proud to announce the Vortex > Library 0.8.11 availability: an open source "BEEP Core" protocol > implementation written in C, mapped onto TCP/IP. congrats! /mtr
El vie, 28-04-2006 a las 17:18 +0200, Marshall Rose escribió: > congrats! Thanks Marshall!! > > /mtr > -- -- Francis Brosnan Blazquez <francis <at> aspl.es> Advanced Software Production Line, S.L.
RSS Feed2 | |
|---|---|
1 | |
1 | |
1 | |
3 | |
2 | |
2 | |
1 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
12 | |
1 | |
4 | |
24 | |
2 | |
1 | |
2 | |
5 | |
2 | |
1 | |
1 | |
7 | |
1 | |
1 | |
2 | |
4 | |
1 | |
1 | |
1 | |
1 | |
2 | |
2 | |
1 | |
4 | |
2 | |
3 | |
1 | |
4 | |
8 | |
4 | |
13 | |
15 | |
3 | |
1 | |
2 | |
1 | |
12 | |
2 | |
10 | |
6 | |
8 | |
3 | |
1 | |
4 | |
15 | |
6 | |
10 | |
5 | |
3 | |
2 | |
1 | |
6 | |
3 | |
16 | |
35 | |
29 | |
27 | |
2 | |
5 |
