| /dpdk/drivers/bus/dpaa/base/qbman/ |
| H A D | bman.h | 104 u32 busy; member 183 rcr->busy = 0; in bm_rcr_init() 219 rcr->busy = 1; in bm_rcr_start() 230 DPAA_ASSERT(rcr->busy); in bm_rcr_abort() 231 rcr->busy = 0; in bm_rcr_abort() 241 DPAA_ASSERT(rcr->busy); in bm_rcr_pend_and_next() 259 DPAA_ASSERT(rcr->busy); in bm_rcr_pci_commit() 268 rcr->busy = 0; in bm_rcr_pci_commit() 288 DPAA_ASSERT(rcr->busy); in bm_rcr_pce_commit() 297 rcr->busy = 0; in bm_rcr_pce_commit() [all …]
|
| H A D | qman.h | 151 u32 busy; member 238 DPAA_ASSERT(!eqcr->busy); in qm_eqcr_start_no_stash() 244 eqcr->busy = 1; in qm_eqcr_start_no_stash() 257 DPAA_ASSERT(!eqcr->busy); in qm_eqcr_start_stash() 268 eqcr->busy = 1; in qm_eqcr_start_stash() 278 DPAA_ASSERT(eqcr->busy); in qm_eqcr_abort() 279 eqcr->busy = 0; in qm_eqcr_abort() 289 DPAA_ASSERT(eqcr->busy); in qm_eqcr_pend_and_next() 323 eqcr->busy = 0; in qm_eqcr_pci_commit() 353 eqcr->busy = 0; in qm_eqcr_pce_commit() [all …]
|
| H A D | qman.c | 360 eqcr->busy = 0; in qm_eqcr_init() 399 DPAA_ASSERT(!eqcr->busy); in qm_eqcr_finish()
|
| /dpdk/drivers/common/qat/ |
| H A D | qat_device.c | 307 int busy = 0; in qat_pci_device_release() local 325 busy = 1; in qat_pci_device_release() 330 busy = 1; in qat_pci_device_release() 335 busy = 1; in qat_pci_device_release() 337 if (busy) in qat_pci_device_release()
|
| /dpdk/lib/vhost/ |
| H A D | fd_man.c | 159 if (i != -1 && pfdset->fd[i].busy == 0) { in fdset_del() 191 if (i != -1 && pfdset->fd[i].busy) { in fdset_try_del() 275 pfdentry->busy = 1; in fdset_event_dispatch() 283 pfdentry->busy = 0; in fdset_event_dispatch()
|
| H A D | fd_man.h | 19 int busy; /* whether this entry is being used in cb. */ member
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | power_man.rst | 117 This means CPU cores always show 100% busy independent of how much work 118 those cores are doing. It is critical to accurately determine how busy 130 When the system become busy, the empty poll mechanism can also increase the core 139 The less the number of empty polls, means current core is busy with processing 155 * HIGH: the frequency is used to process busy traffic workload. 213 This power saving scheme will avoid busy polling by either entering
|
| H A D | efd_lib.rst | 399 runtime inserts, and keys are moved around from a busy group to a less
|
| H A D | packet_framework.rst | 1134 …Once the writer update is done, the writer can signal to the readers and busy wait until all reade…
|
| H A D | rte_flow.rst | 3486 - ``-EBUSY``: action cannot be performed due to busy device resources, may
|
| /dpdk/examples/l2fwd-jobstats/ |
| H A D | main.c | 141 uint64_t busy, busy_min, busy_max; in show_lcore_stats() local 204 busy = exec + management; in show_lcore_stats() 237 cycles_to_ns(busy), busy * 100.0 / stats_period, in show_lcore_stats() 238 cycles_to_ns(loop_count ? busy / loop_count : 0), in show_lcore_stats()
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | l3_forward_power_man.rst | 40 the PMD is still busy waiting for network packets, which wastes a lot of power. 231 of how busy the application is. Empty poll mode can be enabled by the 249 * ``med_threshold`` : optional, sets the empty poll threshold of a modestly busy system state. If t… 251 * ``high_threshold`` : optional, sets the empty poll threshold of a busy system state. If this is n… 300 and busy percentage for each forwarding core. The aggregation of these 304 The busy percentage is calculated by recording the poll_count 307 reference cycles and accordingly busy rate is set to either 0% or 345 to avoid busy looping when there is no traffic.
|
| H A D | vm_power_management.rst | 39 policy can contain time-of-day information for busy/quiet 124 power adjustment (busy/quiet hour power adjustment for example). See 127 One method of power management is to sense how busy a core is when 407 monitoring of branch ratios on cores doing busy polling using PMDs as 543 ``--busy-hours {list of busy hours}`` 560 - TIME - Uses a busy/quiet hours policy. 759 The hours of the day in which we scale up the cores for busy times. 862 depending on busy and quiet hours.
|
| /dpdk/drivers/bus/fslmc/qbman/ |
| H A D | qbman_portal.h | 80 atomic_t busy; member
|
| H A D | qbman_portal.c | 272 atomic_set(&p->vdq.busy, 1); in qbman_swp_init() 1892 if (!atomic_dec_and_test(&s->vdq.busy)) { in qbman_swp_pull_direct() 1893 atomic_inc(&s->vdq.busy); in qbman_swp_pull_direct() 1917 if (!atomic_dec_and_test(&s->vdq.busy)) { in qbman_swp_pull_cinh_direct() 1918 atomic_inc(&s->vdq.busy); in qbman_swp_pull_cinh_direct() 1942 atomic_inc(&s->vdq.busy); in qbman_swp_pull_mem_back() 2080 atomic_inc(&s->vdq.busy); in qbman_swp_dqrr_next_direct() 2155 atomic_inc(&s->vdq.busy); in qbman_swp_dqrr_next_cinh_direct() 2198 atomic_inc(&s->vdq.busy); in qbman_swp_dqrr_next_mem_back() 2243 atomic_inc(&s->vdq.busy); in qbman_result_has_new_result() [all …]
|
| /dpdk/doc/guides/nics/ |
| H A D | af_xdp.rst | 38 * ``busy_budget`` - busy polling budget (optional, default 64); 56 * For busy polling, kernel version v5.11 or later is required.
|
| H A D | hns3.rst | 126 scheduling of the system will be very busy, and the reply of the
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_20_02.rst | 220 dual-thread feature. It was replaced with a threshold feature. At busy times
|
| H A D | release_21_05.rst | 169 * Added support for preferred busy polling.
|