Lines Matching +full:rx +full:- +full:slots

2  * Copyright (c) 2010-2012 Broadcom. All rights reserved.
13  * 3. The names of the above-listed copyright holders may not be used
43 /* Really determined by the message driver, and should be available from a run-time call. */
54 /* Really determined by the message driver, and should be available from a run-time call. */
77  * 1 for host-app, 1 for VMCS, and these are hooked together by a loopback MPHI VCFW
94 /* Adjust if using a message driver that supports more logical RX channels */
99 /* How many receive slots do we use. This times VCHI_MAX_MSG_SIZE gives the effective
109 /* Do we utilise overrun facility for receive message slots? Can aid peer transmit
114 /* How many transmit slots do we use. Generally don't need many, as the hardware driver
120 /* If a service has held or queued received messages in VCHI_XOFF_THRESHOLD or more slots,
131  * VCHI_XON_THRESHOLD slots or fewer. */
144 /* Maximum size of bulk transmission chunks, for each interface type. A trade-off between
154  * with multiple-line frames. Only use if the receiver can cope. */
159 /* How many TX messages can we have pending in our transmit slots. Once exhausted,
165 /* How many RX messages can we have parsed in the receive slots. Once exhausted, parsing
193  * by the peer's hardware - it's the number of outstanding requests that can be queued