Lines Matching refs:from
222 distinguish it from other rings which can be created later in the
375 - **req_id**: echoed back from request
376 - **cmd**: echoed back from request
394 specific socket from this point forward. See [Socket families and
416 - **id**: echoed back from request
438 ring**. The data ring is used to send and receive data from the
484 - **id**: echoed back from request
539 - **id**: echoed back from request
582 - **id**: echoed back from request
620 - **id**: echoed back from request
645 Page and Data ring]. The **data ring** is used to send and receive data from
664 - backend creates an internal mapping from **id_new** to the new socket
691 - **id**: id of the listening socket, echoed back from request
731 - **id**: echoed back from request
856 receiving data from a data ring, and updating the corresponding indexes
909 /* not actually C compliant (ring_order changes from socket to socket) */
927 It contains data read from the socket. The producer is the backend, the
933 Consumer and producer indexes for data read from the socket. They keep track
934 of how much data has already been consumed by the frontend from the **in**
936 **in_cons** is increased by the frontend, after reading data from **in**.
942 increased by the backend, after reading data from **out**.
943 - **in_error** and **out_error** They signal errors when reading from the socket
992 The producer, the backend in this case, never reads from the **in**
998 is already actively reading from the ring. The producer can figure it
1053 - read *[in|out]_cons*, *[in|out]_prod*, *[in|out]_error* from shared memory
1062 The consumer (the backend for **out**, the frontend for **in**) reads from the
1065 - read *[in|out]_prod*, *[in|out]_cons*, *[in|out]_error* from shared memory
1068 - read from array at position *[in|out]_cons* up to *[in|out]_prod*,
1078 reading from the socket.