Searched refs:CQ (Results 1 – 7 of 7) sorted by relevance
| /f-stack/dpdk/doc/guides/eventdevs/ |
| H A D | dlb.rst | 296 In the last stage prior to scheduling an atomic event to a CQ, DLB holds the 302 - All N entries are filled with events from flow X, which is pinned to CQ 0. 304 Until CQ 0 releases 1+ events, no other atomic flows for that LDB queue can be 324 The DLB PMD's default behavior for managing a CQ is to "pop" the CQ once per 326 corresponding entries in the CQ, which enables the DLB to schedule more events 332 the CQ entry is not popped until the *subsequent* rte_event_dequeue_burst()
|
| H A D | dlb2.rst | 320 The DLB2 PMD's default behavior for managing a CQ is to "pop" the CQ once per 322 corresponding entries in the CQ, which enables the DLB2 to schedule more events 328 the CQ entry is not popped until the *subsequent* rte_event_dequeue_burst() 341 In the last stage prior to scheduling an atomic event to a CQ, DLB2 holds the 347 - All N entries are filled with events from flow X, which is pinned to CQ 0. 349 Until CQ 0 releases 1+ events, no other atomic flows for that LDB queue can be
|
| /f-stack/dpdk/doc/guides/vdpadevs/ |
| H A D | mlx5.rst | 116 - 2, Completion queue scheduling will be managed by interrupts. Each CQ burst 117 arms the CQ in order to get an interrupt event in the next traffic burst.
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | ena.rst | 69 SQ correspondingly). Each SQ has a completion queue (CQ) associated
|
| H A D | enic.rst | 45 - The number of CQs should set so that there is one CQ for each 46 WQ, and one CQ for each pair of RQs.
|
| /f-stack/dpdk/drivers/net/ice/base/ |
| H A D | ice_lan_tx_rx.h | 887 #define GLTCLAN_CQ_CNTX(i, CQ) (GLTCLAN_CQ_CNTX0(CQ) + ((i) * 0x0800)) argument
|
| /f-stack/dpdk/doc/guides/rel_notes/ |
| H A D | release_2_1.rst | 972 * **virtio: Fix crash if CQ is not negotiated.**
|