f4cbdbc7fb
Implementation is based on waitable timers Win32 API. When timer is set, a callback and its argument are supplied to the OS, while timer handle is stored in EAL alarm list. When timer expires, OS wakes up the interrupt thread and runs the callback. Upon completion it removes the alarm. Waitable timers must be set from the thread their callback will run in, eal_intr_thread_schedule() provides a way to schedule asyncronuous code execution in the interrupt thread. Alarm module builds synchronous timer setup on top of it. Windows alarms are not a type of DPDK interrupt handle and do not interact with interrupt module beyond executing in the same thread. Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> Acked-by: Narcisa Vasile <navasile@linux.microsoft.com>
25 lines
410 B
Meson
25 lines
410 B
Meson
# SPDX-License-Identifier: BSD-3-Clause
|
|
# Copyright(c) 2019 Intel Corporation
|
|
|
|
subdir('include')
|
|
|
|
sources += files(
|
|
'eal.c',
|
|
'eal_alarm.c',
|
|
'eal_debug.c',
|
|
'eal_file.c',
|
|
'eal_hugepages.c',
|
|
'eal_interrupts.c',
|
|
'eal_lcore.c',
|
|
'eal_log.c',
|
|
'eal_memalloc.c',
|
|
'eal_memory.c',
|
|
'eal_mp.c',
|
|
'eal_thread.c',
|
|
'eal_timer.c',
|
|
'fnmatch.c',
|
|
'getopt.c',
|
|
)
|
|
|
|
dpdk_conf.set10('RTE_EAL_NUMA_AWARE_HUGEPAGES', true)
|