Basic 2-way Arbiter
CE-653 - Handshake Channel Design
27
}Purpose
}Used to control access to shared resource
}Approach
}Acknowledge handshake on request port that arrives first, granting access
}Requires four-phase protocol
}winner maintains mutually-exclusive access of resource until it resets request
}Caveat
}Make take an exponential amount of time to determine who came first when requests arrive very close together
}Sometimes called slackless arbiter
}