Lines Matching refs:request
158 request ring. |
168 - Connect to the request ring and
308 identify one specific request/response pair of commands. Not to be
327 Similarly to other Xen ring based protocols, after writing a request to
375 - **req_id**: echoed back from request
376 - **cmd**: echoed back from request
385 A description of each command, their additional request and response
416 - **id**: echoed back from request
484 - **id**: echoed back from request
539 - **id**: echoed back from request
582 - **id**: echoed back from request
620 - **id**: echoed back from request
637 The **accept** operation extracts the first connection request on the
641 accept request struct (**id_new**). See the [POSIX accept function][accept]
654 The backend will reply to the request only when a new connection is
660 - frontend issues an **accept** request
691 - **id**: id of the listening socket, echoed back from request
731 - **id**: echoed back from request
753 larger than 56 bytes, which is the current size of the request, then the
755 request structure without disrupting the current ABI is to introduce a
757 that the request uses two request slots, for a total of 112 bytes.
981 request size: the producer writes opaque data to the ring. On the other
982 end, in [ring.h] they are combined, and the request size is static and