•The
Ironman abstraction says what is to be transferred and when, but
not how
•Key
idea: 4 procedure calls mark the intervals during which communication can occur
–DR(A) = destination location ready to receive data [R
side]
–SR(A) = source data is ready for transfer [S side]
–DN(A) = destination data is now needed [R side]
–SV(A) = source location is volatile (to be overwritten) [S
side]
•Bound
the interval on the sending (S) and receiving (R) sides of the communication
and let
the hardware implement the communication