Searched refs:reply (Results 1 – 9 of 9) sorted by relevance
/l4re-core-master/l4sys/include/cxx/ |
A D | ipc_server_loop | 42 * The reply mode specifies if the server loop shall do a compound reply 44 * method. Note, setup_wait() is called before the reply. The other 45 * way is to call reply and wait separately and call setup_wait in between. 52 Reply_compound, ///< Server shall use a compound reply and wait (fast). 53 Reply_separate ///< Server shall call reply and wait separately. 75 * Mix in for LOOP_HOOKS to always use compound reply and wait. 327 * incoming messages calls the dispatcher, sends a reply and waits again. 355 /// Internal implementation for reply and wait 363 if (reply.label() != -L4_ENOREPLY) 365 Ipc_svr::Reply_mode m = this->before_reply(reply, utcb); [all …]
|
A D | ipc_server | 188 // XXX: send a reply or just do not reply in case of a cheating client 224 // reply data 228 // reply with the reply data from the server function
|
A D | ipc_epiface | 187 * \retval -L4_ENOREPLY No reply message is send. 188 * \retval <0 Error, reply with error code. 189 * \retval >=0 Success, reply with return value.
|
/l4re-core-master/cxx/lib/ipc/include/ |
A D | ipc_server | 55 * \param ios The Ipc::Iostream for reading the request and writing the reply. 56 * \retval -L4_ENOREPLY Instructs the server loop to not send a reply. 57 * \retval <0 Error, reply with error code. 58 * \retval >=0 Success, reply with return value. 62 * and create a reply by marshalling to the stream (`ios`). For details 66 * before inserting any reply data or before doing any function call 118 * \param ios The message stream for the incoming and the reply message.
|
A D | ipc_timeout_queue | 181 // we must handle the timer only when called after a possible reply 182 // otherwise we probably destroy the reply message. 196 // split up reply and wait when a timeout has expired
|
A D | ipc_stream | 854 * reply in the input stream. 871 * Do an IPC reply and wait. 882 * A reply and wait is usually used by servers that reply to a client 893 * Do an IPC reply and wait. 905 * A reply and wait is usually used by servers that reply to a client 912 inline l4_msgtag_t reply(l4_timeout_t timeout, long proto = 0); 913 inline l4_msgtag_t reply(long proto = 0) 914 { return reply(L4_IPC_SEND_TIMEOUT_0, proto); } 1008 Iostream::reply(l4_timeout_t timeout, long proto)
|
/l4re-core-master/uclibc/lib/contrib/uclibc/libc/inet/rpc/ |
A D | svc_udp.c | 206 char *reply; in svcudp_recv() local 257 if (cache_get (xprt, msg, &reply, &replylen)) in svcudp_recv() 262 iovp->iov_base = reply; in svcudp_recv() 268 (void) sendto (xprt->xp_sock, reply, (int) replylen, 0, in svcudp_recv()
|
/l4re-core-master/l4sys/include/ |
A D | pager | 78 * and generate a reply, potentially filling in `fp`. 116 * for the reply.
|
/l4re-core-master/l4re/include/ |
A D | dataspace | 42 // * size support in map, mapped size in reply
|
Completed in 7 milliseconds