Lines Matching refs:callback

222 Both messages and requests will trigger a named callback on the receiver side.
229 Before any messages can be received, a callback will need to be registered.
231 function accepts a unique callback name, and a function pointer to a callback
232 that will be called when a message or a request matching this callback name
236 specific callback function, ``rte_mp_action_unregister()`` function can be
237 called to ensure that callback will not be triggered again.
245 * ``name`` - message name. This name must match receivers' callback name.
279 For asynchronous requests, a function pointer to the callback function must be
280 provided instead. This callback will be called when the request either has timed
285     When an asynchronous request times out, the callback will be called not by
288     event (such as an alarm) while handling asynchronous IPC callback.
290 When the callback is called, the original request descriptor will be provided
292 callback to), along with a response descriptor like the one described above.
299 To receive a message, a name callback must be registered using the
300 ``rte_mp_action_register()`` function. The name of the callback must match the
302 message to be delivered and for the callback to be trigger.
304 The callback's definition is ``rte_mp_t``, and consists of the incoming message
313     Simply returning a value when processing a request callback will not send a
329 not be mixed: it is not safe to use IPC inside a memory-related callback, nor is
348 If a callback has been registered, IPC will assume that it is safe to call it.
351 the callback has not been registered yet. However, once the callback has been