Lanai Active Messages, release 0.99 pl 14
LAM for LANAI 4.X Boards
Click here for a port of LAM to the 4.x boards. Not for the meek.
This is the first release of Lanai Active Messages. LAM runs on SBUS based Lanai Boards from Myricom
. This release has been tested on a fully configured 32-node system.
Some features of the relase include:
- Conforms to The Generic Active Message Interface Specification.
- By popular demand, extends the GAM spec with three calls:
- am_request_5(): Send that extra word in a pinch.
- am_reply_xfer(): It's back! reply handlers can now push block data back to the source.
- Can exist on the same physical network with Myricom's TCP/IP drivers. (See caveats below)
- A user level network mapper will generaate automatic routing tables and save them to files.
The old release for 2.X LANai boards is no longer supported. Send mail to email@example.com if you want a copy.
to get the source code for the micro-benchmark set only. (112991 bytes)
to get the source code for the mapper (32865 bytes). Compatible with the new LANai 4.X version.
Although running LAM can co-exist with the DLPI drivers from Myricom, the two cannot inter-operate. The a board running LAM looks like a black hole to the mapper running on a Myricom mcp.
Only one process can use a board at a time. This will get fixed in the next release as well.
Mapping and routing is still a chore, though feasable. This process will be completely automated in the next generation of active messages.
Waking up a thread blocked by am_sleep() in Solaris 2.4 takes about 100 usec. Bummer.
- Lok T. Liu
- Vikram Makhija
- Rich Martin
Send Bug(feature) reports to firstname.lastname@example.org