Lines Matching refs:server
42 * \brief Interface for server-loop related functions.
44 * This interface provides access to high-level server-loop related functions,
54 /// Data type expressing server-side demand for receive buffers.
57 /// Make a server interface
60 // Destroy the server interface
64 * \brief Tells the server to allocate buffers for the given demand.
65 * \param demand The total server-side demand of receive buffers needed for
69 * server implementation or the registry implementation calls this function
70 * whenever a new object is registered at the server.
95 * \brief Add a timeout to the server internal timeout queue.
145 * An Epiface is the base interface of objects registered in the server loop.
158 /// Type for abstract server interface.
160 /// Type for server-side receive buffer demand.
179 /// Make a server object
191 * This function must be implemented by application specific server
198 * Get the server-side receive buffer demand for this object.
201 * \return The needed server-side receive buffers for this object
210 * \return Capability for the kernel object behind the server.
217 * Get pointer to server interface at which the object is currently registered.
218 * \return Pointer to the server at which the object is currently registered,
219 * NULL if the object is not registered at any server.
224 * Set server registration info for the object.
225 * \param srv The server to register at
228 * server implementations use this flag to remember whether
245 * Deprecated server registration function.
269 /// Get the server-side buffer demand based in \a IFACE.
275 * \return Capability for the kernel object behind the server.
300 * \return Irq capability for the kernel object behind the server.
317 * \return Irq capability for the kernel object behind the server.
326 * An object registry allows to register L4::Epiface objects at a server
340 * `o` to as a server-side object.
351 * Register `o` as server-side object for synchronous RPC.
353 * server-side object for RPC.
368 * Register `o` as server-side object for asynchronous IRQs.
370 * server-side object for IRQs.
383 * Register `o` as server-side object for a pre-allocated capability.
385 * server-side object.
387 * shall be attached as server-side handler. The capability
398 * Unregister the given object `o` from the server.
533 * \brief This registry returns the corresponding server object
541 * \brief Get the server object for an Ipc_gate label.
549 * \brief The dispatch function called by the server loop.
551 * This function forwards the message to the server object identified by the