GPSHMEM

GPSHMEM

We have completed the basic implementation of the T3D components of the software and added a strided interface to the code. This interface is targeted at moving patches of data via the one-sided interfaces. This interface is notable since it is beyond the original scope of the CRI SHMEM and was unnecessary for the T3D/T3E architecture because of the very low hardware latency. The following functionality is in place:

• T3D collective and one-sided functions.
• T3E shmem_wait functionality. A global, semaphore like wait routine.
• F77 memory management system to allow utilization with older codes and on Linux.
• Built in autoconf mechanisms for easier library management.
• Internal test code for verification of functionality.
• In cooperation with R. Numrich, the original SHMEM developer at Cray, we have used this code on an internal Cray product that has been canceled by the vendor. GPSHMEM would have been their deployed one-sided mechanism for that product had it made it to market.