Loading...
Searching...
No Matches
Server-Side IPC framework
The L4Re IPC Framework

Server-Side framework for implementing object-oriented servers. More...

Collaboration diagram for Server-Side IPC framework:

## Namespaces

namespace | L4::Ipc_svr
| Helper classes for L4::Server instantiation.

## Data Structures

class | L4::Ipc_svr::Server_iface
| Interface for server-loop related functions. More...
class | L4::Basic_registry
| This registry returns the corresponding server object based on the label of an Ipc_gate. More...
struct | L4::Ipc_svr::Ignore_errors
| Mix in for LOOP_HOOKS to ignore IPC errors. More...
struct | L4::Ipc_svr::Default_timeout
| Mix in for LOOP_HOOKS to use a 0 send and a infinite receive timeout. More...
struct | L4::Ipc_svr::Compound_reply
| Mix in for LOOP_HOOKS to always use compound reply and wait. More...
struct | L4::Ipc_svr::Default_setup_wait
| Mix in for LOOP_HOOKS for setup_wait no op. More...
class | L4::Ipc_svr::Br_manager_no_buffers
| Empty implementation of Server_iface. More...
struct | L4::Ipc_svr::Default_loop_hooks
| Default LOOP_HOOKS. More...
class | L4::Server< LOOP_HOOKS >
| Basic server loop for handling client requests. More...
class | L4::Server_object
| Abstract server object to be used with L4::Server and L4::Basic_registry. More...
struct | L4::Server_object_t< IFACE, BASE >
| Base class (template) for server implementing server objects. More...
struct | L4::Server_object_x< Derived, IFACE, BASE >
| Helper class to implement p_dispatch based server objects. More...
struct | L4::Irq_handler_object
| Server object base class for handling IRQ messages. More...
class | L4::Ipc_svr::Timeout
| Callback interface for Timeout_queue. More...
class | L4::Ipc_svr::Timeout_queue
| Timeout queue to be used in l4re server loop. More...
class | L4::Ipc_svr::Timeout_queue_hooks< HOOKS, BR_MAN >
| Loop hooks mixin for integrating a timeout queue into the server loop. More...

## Enumerations

enum | L4::Ipc_svr::Reply_mode { L4::Ipc_svr::Reply_compound , L4::Ipc_svr::Reply_separate }
| Reply mode for server loop. More...

## Detailed Description

Server-Side framework for implementing object-oriented servers.

´

## Enumeration Type Documentation

## Reply_mode

enum L4::Ipc_svr::Reply_mode

Reply mode for server loop.

The reply mode specifies if the server loop shall do a compound reply and wait operation (Reply_compound), which is the most performant method. Note, setup_wait() is called before the reply. The other way is to call reply and wait separately and call setup_wait in between.

The actual mode is determined by the return value of the before_reply() hook in the LOOP_HOOKS of L4::Server.

Enumerator
Reply_compound | Server shall use a compound reply and wait (fast).
Reply_separate | Server shall call reply and wait separately.

Definition at line 46 of file ipc_server_loop.