* local MDs. In particular, they signal the completion of a data transmission
* into or out of a MD. They can also be used to hold acknowledgments for
* completed PUT operations and indicate when a MD has been unlinked. Multiple
- * MDs can share a single EQ. An EQ may have an optional event handler
- * associated with it. If an event handler exists, it will be run for each
- * event that is deposited into the EQ.
+ * MDs can share a single EQ. An EQ must have an event handler
+ * associated with it. It will be run for each event that is deposited into
+ * the EQ.
*
* In addition to the struct lnet_eq, the LNet API defines two types
* associated with events: The ::lnet_event_kind defines the kinds of events
* that can be stored in an EQ. The struct lnet_event defines a structure that
* holds the information about with an event.
*
- * There are three functions for dealing with EQs: LNetEQAlloc() is used
+ * There are two functions for dealing with EQs: LNetEQAlloc() is used
* to create an EQ and allocate the resources needed, while LNetEQFree()
- * releases these resources and free the EQ. LNetEQPoll() can be used
- * to test or wait on multiple EQs.
+ * releases these resources and frees the EQ.
* @{ */
struct lnet_eq *
-LNetEQAlloc(unsigned int count_in,
- lnet_eq_handler_t handler);
+LNetEQAlloc(lnet_eq_handler_t handler);
int LNetEQFree(struct lnet_eq *eventq_in);
-int LNetEQPoll(struct lnet_eq **eventqs_in,
- int neq_in,
- signed long timeout,
- struct lnet_event *event_out,
- int *which_eq_out);
/** @} lnet_eq */
/** \defgroup lnet_data Data movement operations