| /dpdk/app/test/ |
| H A D | test_timer.c | 274 static struct rte_timer *timers; in timer_stress2_main_loop() local
286 timers = rte_malloc(NULL, sizeof(*timers) * NB_STRESS2_TIMERS, 0); in timer_stress2_main_loop()
287 if (timers == NULL) { in timer_stress2_main_loop()
295 rte_timer_init(&timers[i]); in timer_stress2_main_loop()
305 ret = rte_timer_reset(&timers[i], delay, SINGLE, main_lcore, in timer_stress2_main_loop()
353 rte_timer_reset(&timers[i], delay, SINGLE, main_lcore, in timer_stress2_main_loop()
360 rte_timer_stop(&timers[r]); in timer_stress2_main_loop()
361 rte_timer_reset(&timers[r], delay, SINGLE, main_lcore, in timer_stress2_main_loop()
387 if (timers != NULL) { in timer_stress2_main_loop()
388 rte_free(timers); in timer_stress2_main_loop()
[all …]
|
| H A D | test_event_timer_adapter.c | 491 _arm_timers(uint64_t timeout_tcks, uint64_t timers) in _arm_timers() argument
505 for (i = 0; i < timers; i++) { in _arm_timers()
604 _arm_timers_burst(uint64_t timeout_tcks, uint64_t timers) in _arm_timers_burst() argument
619 for (i = 0; i < timers / MAX_BURST; i++) { in _arm_timers_burst()
772 _cancel_producer(uint64_t timeout_tcks, uint64_t timers) in _cancel_producer() argument
786 for (i = 0; i < timers; i++) { in _cancel_producer()
809 _cancel_producer_burst(uint64_t timeout_tcks, uint64_t timers) in _cancel_producer_burst() argument
826 for (i = 0; i < timers / MAX_BURST; i++) { in _cancel_producer_burst()
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | timer_lib.rst | 18 * If not required in the application, timers can be disabled at compilation time by not calling t…
30 with all pending timers for a core being maintained in order of timer expiry in a skiplist data str…
35 up to 4^10 entries, that is, approximately 1,000,000 timers per lcore.
56 …ce in the case where there are entries in the timer list but none of those timers have yet expired,
74 …- The callout facility that provides timers with a mechanism to execute a function at a given time.
|
| H A D | event_timer_adapter.rst | 17 destroyed, and :ref:`event timers <event_timer>` can be armed and canceled.
22 implementation manages timers using the DPDK
33 Event timers are timers that enqueue a timer expiration event to an event
89 timers.
96 And to start and stop timers:
144 to support timers of the respective type. A periodic timer expires at a fixed
202 manage event timers with it.
251 In the special case that there is a set of event timers that should all expire
314 timers or handle timer expiry events.
|
| H A D | glossary.rst | 36 mbuf, timers, and so on.
|
| H A D | kernel_nic_interface.rst | 221 …lowing resource: `Kernel Timers <http://www.kernel.org/doc/Documentation/timers/timers-howto.txt>`_
|
| H A D | multi_proc_support.rst | 187 it may not be possible to have HPET timers available in each DPDK instance.
|
| H A D | env_abstraction_layer.rst | 12 (that is, memory space, devices, timers, consoles, and so on).
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | timer.rst | 8 … application prints some messages from different lcores regularly, demonstrating the use of timers.
70 In the main() function, the two timers are initialized.
79 Then, the two timers are configured:
92 :end-before: >8 End of two timers configured.
|
| H A D | l3_forward_power_man.rst | 128 The Timer library is also initialized and several timers are created later on,
|
| /dpdk/doc/guides/eventdevs/ |
| H A D | cnxk.rst | 38 - HW managed event timers support through TIM, with high precision and
127 Chunks are used to store event timers, a chunk can be visualised as an array
129 store events. TIM traverses the list of chunks and enqueues the event timers
|
| H A D | octeontx.rst | 31 - HW managed event timers support through TIMVF, with high precision and
|
| /dpdk/lib/eal/linux/ |
| H A D | eal_timer.c | 52 } timers[HPET_TIMER_NUM]; /**< Set of HPET timers. */ member
|
| /dpdk/doc/api/ |
| H A D | doxy-api-index.md | 69 - **timers**:
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | enable_func.rst | 109 DPDK can support the system HPET as a timer source rather than the system default timers,
|
| /dpdk/drivers/common/iavf/ |
| H A D | iavf_type.h | 978 u16 timers; member
|
| /dpdk/doc/guides/nics/ |
| H A D | ena.rst | 151 * Watchdog (requires handling of timers in the application)
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | known_issues.rst | 110 HPET timers do not work on the Osage customer reference platform
114 …HPET timers do not work on the Osage customer reference platform which includes an Intel® Xeon® pr…
|
| H A D | release_19_05.rst | 233 timers are being started, stopped, and managed.
|
| H A D | release_21_05.rst | 30 packet processing, timers, cryptography, etc.
|
| H A D | release_18_05.rst | 218 APIs that allow applications to arm/cancel event timers that generate
|
| /dpdk/drivers/net/i40e/base/ |
| H A D | i40e_type.h | 1904 u16 timers; member
|
| /dpdk/doc/guides/tools/ |
| H A D | testeventdev.rst | 142 Number of event timers each producer core will generate.
|