d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
07dcbfe010
numam-dpdk/lib/librte_eal/rte_eal_version.map

287 lines
5.3 KiB
Plaintext
Raw Normal View History

lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
DPDK_2.0 {
global:
__rte_panic;
devargs_list;
eal_parse_sysfs_value;
eal_timer_source;
lcore_config;
per_lcore__lcore_id;
per_lcore__rte_errno;
mem: move librte_malloc to eal/common Move malloc inside eal and create a new section in MAINTAINERS file for Memory Allocation in EAL. Create a dummy malloc library to avoid breaking applications that have librte_malloc in their DT_NEEDED entries. This is the first step towards using malloc to allocate memory directly from memsegs. Thus, memzones would allocate memory through malloc, allowing to free memzones. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-15 16:32:20 +00:00
rte_calloc;
rte_calloc_socket;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_cpu_check_supported;
rte_cpu_get_flag_enabled;
rte_cycles_vmware_tsc_map;
rte_delay_us;
rte_dump_physmem_layout;
rte_dump_registers;
rte_dump_stack;
rte_dump_tailq;
rte_eal_alarm_cancel;
rte_eal_alarm_set;
rte_eal_devargs_add;
rte_eal_devargs_dump;
rte_eal_devargs_type_count;
rte_eal_get_configuration;
rte_eal_get_lcore_state;
rte_eal_get_physmem_size;
rte_eal_has_hugepages;
rte_eal_hpet_init;
rte_eal_init;
eal: fix dynamic link with virtio Building shared libraries and using virtio PMD results in undefined reference to 'rte_eal_iopl_init'. Add missing function to eal version map. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2015-02-12 15:40:54 +00:00
rte_eal_iopl_init;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_eal_lcore_role;
rte_eal_mp_remote_launch;
rte_eal_mp_wait_lcore;
eal: enable port hotplug as default for linux and bsd This patch removes CONFIG_RTE_LIBRTE_EAL_HOTPLUG option, and enables it as default in both Linux and BSD. Also, to support port hotplug, rte_eal_pci_scan() and below missing symbols should be exported to ethdev library. - rte_eal_parse_devargs_str() - rte_eal_pci_close_one() - rte_eal_pci_probe_one() - rte_eal_pci_scan() - rte_eal_vdev_init() - rte_eal_vdev_uninit() Signed-off-by: Tetsuya Mukawa <mukawa@igel.co.jp>
2015-06-30 08:26:51 +00:00
rte_eal_parse_devargs_str;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_eal_process_type;
rte_eal_remote_launch;
rte_eal_tailq_lookup;
tailq: introduce dynamic register system This register system makes it possible to reserve a tailq for the dpdk libraries. The "dynamic" tailqs are right after the "static" tailqs in shared mem. Primary process is responsible for writing the tailq names, so that secondary processes can find them. This is a temp commit, "static" tailqs are removed after conversion of all users in next commits. Signed-off-by: David Marchand <david.marchand@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-03-04 21:50:07 +00:00
rte_eal_tailq_register;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_eal_wait_lcore;
rte_exit;
mem: move librte_malloc to eal/common Move malloc inside eal and create a new section in MAINTAINERS file for Memory Allocation in EAL. Create a dummy malloc library to avoid breaking applications that have librte_malloc in their DT_NEEDED entries. This is the first step towards using malloc to allocate memory directly from memsegs. Thus, memzones would allocate memory through malloc, allowing to free memzones. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-15 16:32:20 +00:00
rte_free;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_get_hpet_cycles;
rte_get_hpet_hz;
rte_get_tsc_hz;
rte_hexdump;
rte_intr_callback_register;
rte_intr_callback_unregister;
rte_intr_disable;
rte_intr_enable;
rte_log;
rte_log_cur_msg_loglevel;
rte_log_cur_msg_logtype;
rte_logs;
mem: move librte_malloc to eal/common Move malloc inside eal and create a new section in MAINTAINERS file for Memory Allocation in EAL. Create a dummy malloc library to avoid breaking applications that have librte_malloc in their DT_NEEDED entries. This is the first step towards using malloc to allocate memory directly from memsegs. Thus, memzones would allocate memory through malloc, allowing to free memzones. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-15 16:32:20 +00:00
rte_malloc;
rte_malloc_dump_stats;
rte_malloc_get_socket_stats;
rte_malloc_set_limit;
rte_malloc_socket;
rte_malloc_validate;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_mem_lock_page;
rte_mem_virt2phy;
rte_memdump;
rte_memory_get_nchannel;
rte_memory_get_nrank;
rte_memzone_dump;
rte_memzone_lookup;
rte_memzone_reserve;
rte_memzone_reserve_aligned;
rte_memzone_reserve_bounded;
rte_memzone_walk;
rte_openlog_stream;
mem: move librte_malloc to eal/common Move malloc inside eal and create a new section in MAINTAINERS file for Memory Allocation in EAL. Create a dummy malloc library to avoid breaking applications that have librte_malloc in their DT_NEEDED entries. This is the first step towards using malloc to allocate memory directly from memsegs. Thus, memzones would allocate memory through malloc, allowing to free memzones. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-15 16:32:20 +00:00
rte_realloc;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_set_application_usage_hook;
eal: clean up export of socket id variable Theres no need to export this variable. Its set and queried from an API call that doesn't exist in the hot path. Instead just export the rte_socket_id symbol and make the variable private to protect it from type changes. We should do this with the other exported variables too, but I think its too late in the release cycle to do that. tested using distributor_autotest (which uses rte_socket_id), successfully. Only tested on linux, as I don't currently have a bsd system spun up, but the changes are symmetric, and should be fine Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Cunming Liang <cunming.liang@intel.com> Acked-by: David Marchand <david.marchand@6wind.com>
2015-02-27 12:33:13 +00:00
rte_socket_id;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_strerror;
rte_strsplit;
eal: fix missing symbol in version map As per_lcore__socket_id and rte_sys_gettid are missing in version map, it causes compiling error when CONFIG_RTE_BUILD_SHARED_LIB is enabled. Fixes: ef76436c6834 ("eal: get unique thread id") Fixes: 9e29251b2afa ("eal: thread affinity API") Reported-by: Tetsuya Mukawa <mukawa@igel.co.jp> Signed-off-by: Cunming Liang <cunming.liang@intel.com> Tested-by: Tetsuya Mukawa <mukawa@igel.co.jp> Acked-by: John McNamara <john.mcnamara@intel.com>
2015-02-25 03:39:48 +00:00
rte_sys_gettid;
eal: thread affinity API 1. add two TLS *_socket_id* and *_cpuset* 2. add one internal API, eal_cpu_socket_id/eal_thread_dump_affinity 3. add two public API, rte_thread_set/get_affinity 4. update EAL version map for EAL public API The API works for both EAL thread and non EAL thread. When calling rte_thread_set_affinity, the *_socket_id* and *_cpuset* of calling thread will be updated if the thread successfully set the cpu affinity. Signed-off-by: Cunming Liang <cunming.liang@intel.com> Acked-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2015-02-17 02:08:03 +00:00
rte_thread_get_affinity;
rte_thread_set_affinity;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_vlog;
mem: move librte_malloc to eal/common Move malloc inside eal and create a new section in MAINTAINERS file for Memory Allocation in EAL. Create a dummy malloc library to avoid breaking applications that have librte_malloc in their DT_NEEDED entries. This is the first step towards using malloc to allocate memory directly from memsegs. Thus, memzones would allocate memory through malloc, allowing to free memzones. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-15 16:32:20 +00:00
rte_zmalloc;
rte_zmalloc_socket;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
local: *;
};
mem: introduce memzone freeing Implement rte_memzone_free which, as its name implies, would free a memzone. Currently memzone are tracked in an array and cannot be free. To be able to reuse the same array to track memzones, we have to change how we keep track of reserved memzones. With this patch, any memzone with addr NULL is not used, so we also need to change how we look for the next memzone entry free. Add new unit test for rte_memzone_free API. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-15 16:32:25 +00:00
DPDK_2.1 {
global:
eal/bsd: fix missing interrupt stub functions A number of interrupt functions only existed on Linux. Adding in stubs for these functions corrects this omission, and allows the map files for both Linux and FreeBSD to be identical. Fixes: 9efe9c6cdcac ("eal/linux: add epoll wrappers") Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2017-10-19 16:36:26 +00:00
rte_epoll_ctl;
rte_epoll_wait;
eal/linux: add interrupt API for drivers The patch exposes intr event fd create and release for PMD. The device driver can assign the number of event associated with interrupt vector. It also provides misc functions to check 1) allows other slowpath intr(e.g. lsc); 2) intr event on fastpath is enabled or not. Signed-off-by: Cunming Liang <cunming.liang@intel.com>
2015-07-20 03:02:22 +00:00
rte_intr_allow_others;
rte_intr_dp_is_en;
rte_intr_efd_disable;
rte_intr_efd_enable;
eal/linux: add Rx interrupt control function The patch adds 'rte_intr_rx_ctl' to add or delete interrupt vector events monitor on specified epoll instance. Signed-off-by: Cunming Liang <cunming.liang@intel.com>
2015-07-20 03:02:19 +00:00
rte_intr_rx_ctl;
eal/bsd: fix missing interrupt stub functions A number of interrupt functions only existed on Linux. Adding in stubs for these functions corrects this omission, and allows the map files for both Linux and FreeBSD to be identical. Fixes: 9efe9c6cdcac ("eal/linux: add epoll wrappers") Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2017-10-19 16:36:26 +00:00
rte_intr_tls_epfd;
mem: introduce memzone freeing Implement rte_memzone_free which, as its name implies, would free a memzone. Currently memzone are tracked in an array and cannot be free. To be able to reuse the same array to track memzones, we have to change how we keep track of reserved memzones. With this patch, any memzone with addr NULL is not used, so we also need to change how we look for the next memzone entry free. Add new unit test for rte_memzone_free API. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-15 16:32:25 +00:00
rte_memzone_free;
pci: fix detach and uninit naming There are close and detach functions in ethdev. To keep a consistent naming, PCI functions called by ethdev detach must be named "detach" instead of "close". Fix also comments which mix close and uninit names. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-07-18 18:35:57 +00:00
mem: introduce memzone freeing Implement rte_memzone_free which, as its name implies, would free a memzone. Currently memzone are tracked in an array and cannot be free. To be able to reuse the same array to track memzones, we have to change how we keep track of reserved memzones. With this patch, any memzone with addr NULL is not used, so we also need to change how we look for the next memzone entry free. Add new unit test for rte_memzone_free API. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-15 16:32:25 +00:00
} DPDK_2.0;
eal: query multi-vector interrupt capability VFIO allows multiple MSI-X vector, others doesn't, but maybe will allow it in the future. Device drivers need to be aware of the capability. It's better to avoid condition check on interrupt type (VFIO) everywhere, instead a capability api is more flexible for the condition change. Signed-off-by: Cunming Liang <cunming.liang@intel.com> Acked-by: David Marchand <david.marchand@6wind.com>
2015-11-04 08:45:34 +00:00
DPDK_2.2 {
global:
rte_intr_cap_multiple;
eal: add keep alive monitoring Adds functions for detecting and reporting the live-ness of LCores, the primary requirement of which is minimal overheads for the core(s) being checked. Core failures are notified via an application defined callback. Signed-off-by: Remy Horton <remy.horton@intel.com>
2015-11-18 14:05:14 +00:00
rte_keepalive_create;
rte_keepalive_dispatch_pings;
rte_keepalive_mark_alive;
rte_keepalive_register_core;
eal: query multi-vector interrupt capability VFIO allows multiple MSI-X vector, others doesn't, but maybe will allow it in the future. Device drivers need to be aware of the capability. It's better to avoid condition check on interrupt type (VFIO) everywhere, instead a capability api is more flexible for the condition change. Signed-off-by: Cunming Liang <cunming.liang@intel.com> Acked-by: David Marchand <david.marchand@6wind.com>
2015-11-04 08:45:34 +00:00
eal: add keep alive monitoring Adds functions for detecting and reporting the live-ness of LCores, the primary requirement of which is minimal overheads for the core(s) being checked. Core failures are notified via an application defined callback. Signed-off-by: Remy Horton <remy.horton@intel.com>
2015-11-18 14:05:14 +00:00
} DPDK_2.1;
eal: move cpu flags out of headers Move cpu_feature_table array from arch specific rte_cpuflags.h files to new arch specific rte_cpuflags.c files. Main motivation is to escape from static variable declarations in header files. cpu_feature_table has many copies in final binary, even exist in some object files that does not use this variable at all. And this can be a sample to create architecture specific source files and move some functions which are not performance sensitive from architecture header files to source files. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2016-01-28 12:20:23 +00:00
eal: fix symbol map version number The version 2.3 has been renamed 16.04. Fixes: 6d7de6d2e357 ("version: switch to year.month numbers") Reported-by: Panu Matilainen <pmatilai@redhat.com> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-03-01 07:45:38 +00:00
DPDK_16.04 {
eal: move cpu flags out of headers Move cpu_feature_table array from arch specific rte_cpuflags.h files to new arch specific rte_cpuflags.c files. Main motivation is to escape from static variable declarations in header files. cpu_feature_table has many copies in final binary, even exist in some object files that does not use this variable at all. And this can be a sample to create architecture specific source files and move some functions which are not performance sensitive from architecture header files to source files. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2016-01-28 12:20:23 +00:00
global:
eal: get CPU flag name The new function rte_cpu_get_flag_name() is added to the EAL API. It is implemented (duplicated) in each arch because the next patch will remove the public exposure of the feature tables. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-02-02 22:59:49 +00:00
rte_cpu_get_flag_name;
eal: check if primary process is alive This patch adds a new function to the EAL API: int rte_eal_primary_proc_alive(const char *path); The function indicates if a primary process is alive right now. This functionality is implemented by testing for a write- lock on the config file, and the function tests for a lock. The use case for this functionality is that a secondary process can wait until a primary process starts by polling the function and waiting. When the primary is running, the secondary continues to poll to detect if the primary process has quit unexpectedly, the secondary process can detect this. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Maryam Tahhan <maryam.tahhan@intel.com>
2016-03-09 13:37:25 +00:00
rte_eal_primary_proc_alive;
eal: move cpu flags out of headers Move cpu_feature_table array from arch specific rte_cpuflags.h files to new arch specific rte_cpuflags.c files. Main motivation is to escape from static variable declarations in header files. cpu_feature_table has many copies in final binary, even exist in some object files that does not use this variable at all. And this can be a sample to create architecture specific source files and move some functions which are not performance sensitive from architecture header files to source files. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2016-01-28 12:20:23 +00:00
} DPDK_2.2;
pci: allow to override sysfs path The SYSFS_PCI_DEVICES is a constant that makes the PCI testing difficult as it points to an absolute path. We remove using this constant and introducing a function pci_get_sysfs_path that gives the same value. However, the user can pass a SYSFS_PCI_DEVICES env variable to override the path. It is now possible to create a fake sysfs hierarchy for testing. Signed-off-by: Jan Viktorin <viktorin@rehivetech.com>
2016-06-13 15:07:44 +00:00
DPDK_16.07 {
global:
keepalive: fix missing symbol export The KeepAlive rte_keepalive_mark_sleep function was not being exported. Fixes: 90c622f35679 ("keepalive: add liveness callback") Signed-off-by: Remy Horton <remy.horton@intel.com>
2016-06-20 09:59:00 +00:00
rte_keepalive_mark_sleep;
keepalive: fix exported symbols The function rte_keepalive_register_alive_callback do not exist. The function rte_keepalive_register_relay_callback was missing for BSD. Fixes: 90c622f35679 ("keepalive: add liveness callback") Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-06-17 15:00:22 +00:00
rte_keepalive_register_relay_callback;
spinlock: move constructor out of x86 header file Having constructor function in the header file is generally a bad idea, as it will eventually be implanted to 3rd party library. In this case it causes linking issues with 3rd party libraries when an application is not linked to dpdk, due to missing symbol called by constructor. Fixes: ba7468997ea6 ("spinlock: add HTM lock elision for x86") Signed-off-by: Damjan Marion <damarion@cisco.com> Reviewed-by: Jan Viktorin <viktorin@rehivetech.com> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-07-14 13:27:29 +00:00
rte_rtm_supported;
eal: fix thread naming on FreeBSD rte_thread_setname was a macro defined only for Linux. The function rte_thread_setname() can now be used on FreeBSD as well on Linux. It is required to build librte_pdump. The macro was 0 for old glibc. The function is now returning -1. The related logs are decreased from error to debug level because it is not an important failure, just a debug inconvenience. Fixes: 278f945402c5 ("pdump: add new library for packet capture") Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: David Marchand <david.marchand@6wind.com>
2016-06-17 12:48:16 +00:00
rte_thread_setname;
pci: allow to override sysfs path The SYSFS_PCI_DEVICES is a constant that makes the PCI testing difficult as it points to an absolute path. We remove using this constant and introducing a function pci_get_sysfs_path that gives the same value. However, the user can pass a SYSFS_PCI_DEVICES env variable to override the path. It is now possible to create a fake sysfs hierarchy for testing. Signed-off-by: Jan Viktorin <viktorin@rehivetech.com>
2016-06-13 15:07:44 +00:00
} DPDK_16.04;
eal: customize delay function When running single-core, some drivers tend to call rte_delay_us for a long time, and that is causing packet drops. To avoid this, rte_delay_us can be replaced with user-defined delay function with: void rte_delay_us_callback_register(void(*userfunc)(unsigned)); When userfunc==rte_delay_us_block build-in blocking delay function is restored. Signed-off-by: Jozef Martiniak <jozmarti@cisco.com>
2016-09-26 08:35:09 +00:00
DPDK_16.11 {
global:
rte_delay_us_block;
rte_delay_us_callback_register;
eal: add hotplug operations for PCI and vdev Hotplug invocations, which deals with devices, should come from the layer that already handles them, i.e. EAL. For both attach and detach operations, 'name' is used to select the bus that will handle the request. Signed-off-by: David Marchand <david.marchand@6wind.com> Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2016-09-20 12:41:24 +00:00
rte_eal_dev_attach;
rte_eal_dev_detach;
eal: customize delay function When running single-core, some drivers tend to call rte_delay_us for a long time, and that is causing packet drops. To avoid this, rte_delay_us can be replaced with user-defined delay function with: void rte_delay_us_callback_register(void(*userfunc)(unsigned)); When userfunc==rte_delay_us_block build-in blocking delay function is restored. Signed-off-by: Jozef Martiniak <jozmarti@cisco.com>
2016-09-26 08:35:09 +00:00
} DPDK_16.07;
bus: introduce bus abstraction This patch introduces the rte_bus abstraction for EAL. The model is: - One or more devices are connected to a Bus - Drivers are running instances which manage one or more devices - Bus is responsible for identifying devices (and interrupt propogation) - Driver is responsible for initializing the device This patch adds a 'rte_bus' base class which would be extended for specific implementations. It also introduces Bus registration and deregistration functions. Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2017-01-18 14:05:17 +00:00
DPDK_17.02 {
global:
rte_bus_dump;
bus: add probing Bus implementations can implement a probe handler to match the devices scanned against the drivers registered. Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2017-01-18 14:05:22 +00:00
rte_bus_probe;
bus: introduce bus abstraction This patch introduces the rte_bus abstraction for EAL. The model is: - One or more devices are connected to a Bus - Drivers are running instances which manage one or more devices - Bus is responsible for identifying devices (and interrupt propogation) - Driver is responsible for initializing the device This patch adds a 'rte_bus' base class which would be extended for specific implementations. It also introduces Bus registration and deregistration functions. Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2017-01-18 14:05:17 +00:00
rte_bus_register;
bus: add scanning Scan for bus discovers the devices available on the bus and adds them to a bus specific device list. Each bus mandatorily implements this method. Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2017-01-18 14:05:21 +00:00
rte_bus_scan;
bus: introduce bus abstraction This patch introduces the rte_bus abstraction for EAL. The model is: - One or more devices are connected to a Bus - Drivers are running instances which manage one or more devices - Bus is responsible for identifying devices (and interrupt propogation) - Driver is responsible for initializing the device This patch adds a 'rte_bus' base class which would be extended for specific implementations. It also introduces Bus registration and deregistration functions. Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2017-01-18 14:05:17 +00:00
rte_bus_unregister;
} DPDK_16.11;
eal: support dynamic log types Introduce 2 new functions to support dynamic log types: - rte_log_register(): register a log name, and return a log type id - rte_log_set_level(): set the log level of a given log type Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
2017-04-04 16:40:33 +00:00
DPDK_17.05 {
global:
eal: add missing function to symbol map This function rte_cpu_is_supported is now part of the public ABI, so should be advertised as such. Fixes: 37e97ad2c56a ("eal: do not panic when CPU is not supported") Signed-off-by: Aaron Conole <aconole@redhat.com>
2017-04-04 15:38:57 +00:00
rte_cpu_is_supported;
eal/bsd: fix missing interrupt stub functions A number of interrupt functions only existed on Linux. Adding in stubs for these functions corrects this omission, and allows the map files for both Linux and FreeBSD to be identical. Fixes: 9efe9c6cdcac ("eal/linux: add epoll wrappers") Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2017-10-19 16:36:26 +00:00
rte_intr_free_epoll_fd;
eal: dump registered log types Introduce a function to dump the global level and the registered log types. Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
2017-04-04 16:40:34 +00:00
rte_log_dump;
eal: deprecate log functions Deprecate the following functions: - rte_set_log_level(), replaced by rte_log_set_global_level() - rte_get_log_level(), replaced by rte_log_get_global_level() - rte_set_log_type(), replaced by rte_log_set_level() - rte_get_log_type(), replaced by rte_log_get_level() The new functions provide a better control of the per-type log level, and have a better name prefix (rte_log_). Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
2017-04-04 16:40:37 +00:00
rte_log_get_global_level;
eal/bsd: fix missing interrupt stub functions A number of interrupt functions only existed on Linux. Adding in stubs for these functions corrects this omission, and allows the map files for both Linux and FreeBSD to be identical. Fixes: 9efe9c6cdcac ("eal/linux: add epoll wrappers") Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2017-10-19 16:36:26 +00:00
rte_log_register;
eal: deprecate log functions Deprecate the following functions: - rte_set_log_level(), replaced by rte_log_set_global_level() - rte_get_log_level(), replaced by rte_log_get_global_level() - rte_set_log_type(), replaced by rte_log_set_level() - rte_get_log_type(), replaced by rte_log_get_level() The new functions provide a better control of the per-type log level, and have a better name prefix (rte_log_). Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
2017-04-04 16:40:37 +00:00
rte_log_set_global_level;
eal: support dynamic log types Introduce 2 new functions to support dynamic log types: - rte_log_register(): register a log name, and return a log type id - rte_log_set_level(): set the log level of a given log type Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
2017-04-04 16:40:33 +00:00
rte_log_set_level;
eal: change several log levels matching a regexp Introduce a function to set the log level of several log types that match a regular expression. Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
2017-04-04 16:40:35 +00:00
rte_log_set_level_regexp;
vfio: export utility functions in map file adding extra vfio utility functions to map file. They will be used by other vfio supported buses like fslmc bus for NXP DPAA2 devices Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2017-04-11 13:37:13 +00:00
vfio_get_container_fd;
vfio_get_group_fd;
vfio_get_group_no;
eal: support dynamic log types Introduce 2 new functions to support dynamic log types: - rte_log_register(): register a log name, and return a log type id - rte_log_set_level(): set the log level of a given log type Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
2017-04-04 16:40:33 +00:00
} DPDK_17.02;
bus: add iterator to find a bus This helper allows to iterate over all registered buses and find one matching data used as parameter. Signed-off-by: Jan Blunck <jblunck@infradead.org> Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2017-06-30 18:19:30 +00:00
DPDK_17.08 {
global:
rte_bus_find;
bus: add helper to find which bus holds a device Signed-off-by: Jan Blunck <jblunck@infradead.org> Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2017-06-30 18:19:35 +00:00
rte_bus_find_by_device;
bus: add helper to find bus by name Signed-off-by: Jan Blunck <jblunck@infradead.org>
2017-06-30 18:19:37 +00:00
rte_bus_find_by_name;
log: get level for dynamic types This function wasn't provided in the original commit. Fixes: 4f0981e6ec6c ("eal: deprecate log functions") Cc: stable@dpdk.org Signed-off-by: Chas Williams <ciwillia@brocade.com>
2017-07-22 20:07:33 +00:00
rte_log_get_level;
bus: add iterator to find a bus This helper allows to iterate over all registered buses and find one matching data used as parameter. Signed-off-by: Jan Blunck <jblunck@infradead.org> Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2017-06-30 18:19:30 +00:00
} DPDK_17.05;
eal: add hotplug add/remove device Signed-off-by: Jan Blunck <jblunck@infradead.org>
2017-06-30 18:19:41 +00:00
eal: fix version map experimental section Before this commit, the EXPERIMENTAL version of ABI derived from the DPDK_17.08 tag. In parallel there was a DPDK_17.11 tag. Experimental map should always derive from the latest ABI, so this patch moves the 17.11 section above EXPERIMENTAL, and updates EXPERIMENTAL to derive from the 17.11 map. Fixes: aadc3eb002d3 ("pci: export match function") Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
2017-10-25 12:29:49 +00:00
DPDK_17.11 {
global:
rte_eal_create_uio_dev;
rte_bus_get_iommu_class;
rte_eal_has_pci;
rte_eal_iova_mode;
rte_eal_mbuf_default_mempool_ops;
rte_eal_using_phys_addrs;
rte_eal_vfio_intr_mode;
rte_lcore_has_role;
rte_malloc_virt2iova;
rte_mem_virt2iova;
rte_vfio_enable;
rte_vfio_is_enabled;
rte_vfio_noiommu_is_enabled;
rte_vfio_release_device;
rte_vfio_setup_device;
} DPDK_17.08;
eal/x86: get hypervisor name The CPUID instruction is caught by hypervisor which can return a flag indicating one is running, and its name. Suggested-by: Stephen Hemminger <sthemmin@microsoft.com> Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-11-30 21:27:01 +00:00
DPDK_18.02 {
global:
rte_hypervisor_get;
rte_hypervisor_get_name;
vfio: expose clear group function for internal usages other vfio based module e.g. fslmc will also need to use the clear_group call. So, exposing it and renaming it to *rte_vfio_clear_group* Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-01-15 05:11:25 +00:00
rte_vfio_clear_group;
eal: introduce integer divide through reciprocal In some use cases of integer division, denominator remains constant and numerator varies. It is possible to optimize division for such specific scenarios. The librte_sched uses rte_reciprocal to optimize division so, moving it to eal/common would allow other libraries and applications to use it. Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
2018-01-26 05:04:49 +00:00
rte_reciprocal_value;
eal: add u64-bit variant for reciprocal divide Currently, rte_reciprocal only supports unsigned 32bit divisors. This commit adds support for unsigned 64bit divisors. Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
2018-01-26 05:04:50 +00:00
rte_reciprocal_value_u64;
} DPDK_17.11;
eal/x86: get hypervisor name The CPUID instruction is caught by hypervisor which can return a flag indicating one is running, and its name. Suggested-by: Stephen Hemminger <sthemmin@microsoft.com> Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-11-30 21:27:01 +00:00
eal: add hotplug add/remove device Signed-off-by: Jan Blunck <jblunck@infradead.org>
2017-06-30 18:19:41 +00:00
EXPERIMENTAL {
global:
eal: add function to release internal resources This commit adds a new function rte_eal_cleanup(). The function serves as a hook to allow DPDK to release internal resources (e.g.: hugepage allocations). This function allows DPDK to become more like an ordinary library, where the library context itself can be initialized and cleaned up by the application. The rte_exit() and rte_panic() functions must be considered, particularly if they should call rte_eal_cleanup() to release any resources or not. This patch adds the cleanup to rte_exit(), but does not clean up on rte_panic(). The reason to not clean up on panicing is that the developer may wish to inspect the exact internal state of EAL and hugepages. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Vipin Varghese <vipin.varghese@intel.com>
2018-01-29 16:37:30 +00:00
rte_eal_cleanup;
devargs: introduce insert function Some buses will operate either in whitelist or blacklist mode. This mode is currently passed down by the rte_eal_devargs_add function with the devtype argument. When inserting devices using the hotplug API, the implicit assumption is that this device is being whitelisted, meaning that it is explicitly requested by the application to be used. This can conflict with the initial bus configuration. While the rte_eal_devargs_add API is being deprecated soon, it cannot be modified at the moment to accommodate this situation. As such, this new experimental API offers a bare interface for inserting rte_devargs without directly manipulating the global rte_devargs list. This new function expects a fully-formed rte_devargs, previously parsed and allocated. It does not check whether the new rte_devargs is compatible with current bus configuration, but will replace any eventual existing one for the same device, allowing the hotplug operation to proceed. i.e. a previously blacklisted device can be redefined as being whitelisted. Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2017-07-15 17:56:37 +00:00
rte_eal_devargs_insert;
devargs: introduce new parsing helper Introduce a more versatile helper to parse device strings. This helper expects a generic rte_devargs structure as storage in order not to require API changes in the future, should this structure be updated. The old equivalent function is thus being deprecated, as its API does not allow to accompany rte_devargs evolutions. A deprecation notice is issued. This new helper will parse bus information as well as device name and device parameters. It does not allocate an rte_devargs structure and expects one to be given as input. Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2017-07-07 00:04:33 +00:00
rte_eal_devargs_parse;
devargs: introduce removal function Hotplug support introduces the possibility of removing devices from the system. Allocated resources must be freed. Extend the rte_devargs API to allow freeing allocated resources. This API is experimental and bound to change. It is currently designed as a symetrical to rte_eal_devargs_add(), but the latter will evolve shortly anyway. Its DEVTYPE parameter is currently only used to specify scan policies, and those will evolve in the next release. This evolution should rationalize the rte_devargs API. As such, the proposed API here is not the most convenient, but is taylored to follow the current design and integrate easily with its main use within rte_eal_hotplug_* functions. Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2017-07-15 17:56:36 +00:00
rte_eal_devargs_remove;
eal: add hotplug add/remove device Signed-off-by: Jan Blunck <jblunck@infradead.org>
2017-06-30 18:19:41 +00:00
rte_eal_hotplug_add;
rte_eal_hotplug_remove;
mbuf: fix logic of user mempool ops API The existing rte_eal_mbuf_default mempool ops can return the compile time default ops name if the user has not provided command line inputs for mempool ops name. It will break the logic of best mempool ops as it will never return platform hw mempool ops. This patch introduces a new API to just return the user mempool ops only. Fixes: 8b0f7f434132 ("mbuf: maintain user and compile time mempool ops name") Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2018-02-02 08:03:01 +00:00
rte_eal_mbuf_user_pool_ops;
eal: add shared indexed file-backed array rte_fbarray is a simple indexed array stored in shared memory via mapping files into memory. Rationale for its existence is the following: since we are going to map memory page-by-page, there could be quite a lot of memory segments to keep track of (for smaller page sizes, page count can easily reach thousands). We can't really make page lists truly dynamic and infinitely expandable, because that involves reallocating memory (which is a big no-no in multiprocess). What we can do instead is have a maximum capacity as something really, really large, and decide at allocation time how big the array is going to be. We map the entire file into memory, which makes it possible to use fbarray as shared memory, provided the structure itself is allocated in shared memory. Per-fbarray locking is also used to avoid index data races (but not contents data races - that is up to user application to synchronize). In addition, in understanding that we will frequently need to scan this array for free space and iterating over array linearly can become slow, rte_fbarray provides facilities to index array's usage. The following use cases are covered: - find next free/used slot (useful either for adding new elements to fbarray, or walking the list) - find starting index for next N free/used slots (useful for when we want to allocate chunk of VA-contiguous memory composed of several pages) - find how many contiguous free/used slots there are, starting from specified index (useful for when we want to figure out how many pages we have until next hole in allocated memory, to speed up some bulk operations where we would otherwise have to walk the array and add pages one by one) This is accomplished by storing a usage mask in-memory, right after the data section of the array, and using some bit-level magic to figure out the info we need. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Tested-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
2018-04-11 12:30:23 +00:00
rte_fbarray_attach;
rte_fbarray_destroy;
rte_fbarray_detach;
rte_fbarray_dump_metadata;
rte_fbarray_find_idx;
rte_fbarray_find_next_free;
rte_fbarray_find_next_used;
rte_fbarray_find_next_n_free;
rte_fbarray_find_next_n_used;
rte_fbarray_find_contig_free;
rte_fbarray_find_contig_used;
rte_fbarray_get;
rte_fbarray_init;
rte_fbarray_is_used;
rte_fbarray_set_free;
rte_fbarray_set_used;
eal: register log type and pick level from args Dynamic log types are registered on RTE_INIT() step. This allows one to set log levels by EAL options on application launch. However, this does not allow to manage log types if they are created during runtime. EAL does not store log levels and types passed from the command line. Thus, they cannot be picked later. This is an obvious flaw since it would be better to be able to pick levels for dynamic types registered for runtime-determined facilities such as NIC ports. This patch provides a mechanism to store log levels passed from EAL options and adds an API to register log types and pick levels from the internal storage. Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com> Reviewed-by: Andy Moreton <amoreton@solarflare.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-03-21 11:28:16 +00:00
rte_log_register_type_and_pick_level;
malloc: add function to dump heap contents Malloc heap is now a doubly linked list, so it's now possible to iterate over each malloc element regardless of its state. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Tested-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
2018-04-11 12:29:39 +00:00
rte_malloc_dump_heaps;
mem: add iova2virt function This is reverse lookup of PA to VA. Using this will make other code less dependent on internals of mem API. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Tested-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
2018-04-11 12:30:11 +00:00
rte_mem_iova2virt;
mem: add virt2memseg function This can be used as a virt2iova function that only looks up memory that is owned by DPDK (as opposed to doing pagemap walks). Using this will result in less dependency on internals of mem API. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Tested-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
2018-04-11 12:30:15 +00:00
rte_mem_virt2memseg;
mem: replace memseg with memseg lists Before, we were aggregating multiple pages into one memseg, so the number of memsegs was small. Now, each page gets its own memseg, so the list of memsegs is huge. To accommodate the new memseg list size and to keep the under-the-hood workings sane, the memseg list is now not just a single list, but multiple lists. To be precise, each hugepage size available on the system gets one or more memseg lists, per socket. In order to support dynamic memory allocation, we reserve all memory in advance (unless we're in 32-bit legacy mode, in which case we do not preallocate memory). As in, we do an anonymous mmap() of the entire maximum size of memory per hugepage size, per socket (which is limited to either RTE_MAX_MEMSEG_PER_TYPE pages or RTE_MAX_MEM_MB_PER_TYPE megabytes worth of memory, whichever is the smaller one), split over multiple lists (which are limited to either RTE_MAX_MEMSEG_PER_LIST memsegs or RTE_MAX_MEM_MB_PER_LIST megabytes per list, whichever is the smaller one). There is also a global limit of CONFIG_RTE_MAX_MEM_MB megabytes, which is mainly used for 32-bit targets to limit amounts of preallocated memory, but can be used to place an upper limit on total amount of VA memory that can be allocated by DPDK application. So, for each hugepage size, we get (by default) up to 128G worth of memory, per socket, split into chunks of up to 32G in size. The address space is claimed at the start, in eal_common_memory.c. The actual page allocation code is in eal_memalloc.c (Linux-only), and largely consists of copied EAL memory init code. Pages in the list are also indexed by address. That is, in order to figure out where the page belongs, one can simply look at base address for a memseg list. Similarly, figuring out IOVA address of a memzone is a matter of finding the right memseg list, getting offset and dividing by page size to get the appropriate memseg. This commit also removes rte_eal_dump_physmem_layout() call, according to deprecation notice [1], and removes that deprecation notice as well. On 32-bit targets due to limited VA space, DPDK will no longer spread memory to different sockets like before. Instead, it will (by default) allocate all of the memory on socket where master lcore is. To override this behavior, --socket-mem must be used. The rest of the changes are really ripple effects from the memseg change - heap changes, compile fixes, and rewrites to support fbarray-backed memseg lists. Due to earlier switch to _walk() functions, most of the changes are simple fixes, however some of the _walk() calls were switched to memseg list walk, where it made sense to do so. Additionally, we are also switching locks from flock() to fcntl(). Down the line, we will be introducing single-file segments option, and we cannot use flock() locks to lock parts of the file. Therefore, we will use fcntl() locks for legacy mem as well, in case someone is unfortunate enough to accidentally start legacy mem primary process alongside an already working non-legacy mem-based primary process. [1] http://dpdk.org/dev/patchwork/patch/34002/ Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Tested-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
2018-04-11 12:30:24 +00:00
rte_mem_virt2memseg_list;
mem: add contig walk function This function is meant to walk over first segment of each VA-contiguous group of memsegs. For future users of this function, this is done so that there is less dependency on internals of mem API and less noise later change sets. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Tested-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
2018-04-11 12:30:09 +00:00
rte_memseg_contig_walk;
mem: replace memseg with memseg lists Before, we were aggregating multiple pages into one memseg, so the number of memsegs was small. Now, each page gets its own memseg, so the list of memsegs is huge. To accommodate the new memseg list size and to keep the under-the-hood workings sane, the memseg list is now not just a single list, but multiple lists. To be precise, each hugepage size available on the system gets one or more memseg lists, per socket. In order to support dynamic memory allocation, we reserve all memory in advance (unless we're in 32-bit legacy mode, in which case we do not preallocate memory). As in, we do an anonymous mmap() of the entire maximum size of memory per hugepage size, per socket (which is limited to either RTE_MAX_MEMSEG_PER_TYPE pages or RTE_MAX_MEM_MB_PER_TYPE megabytes worth of memory, whichever is the smaller one), split over multiple lists (which are limited to either RTE_MAX_MEMSEG_PER_LIST memsegs or RTE_MAX_MEM_MB_PER_LIST megabytes per list, whichever is the smaller one). There is also a global limit of CONFIG_RTE_MAX_MEM_MB megabytes, which is mainly used for 32-bit targets to limit amounts of preallocated memory, but can be used to place an upper limit on total amount of VA memory that can be allocated by DPDK application. So, for each hugepage size, we get (by default) up to 128G worth of memory, per socket, split into chunks of up to 32G in size. The address space is claimed at the start, in eal_common_memory.c. The actual page allocation code is in eal_memalloc.c (Linux-only), and largely consists of copied EAL memory init code. Pages in the list are also indexed by address. That is, in order to figure out where the page belongs, one can simply look at base address for a memseg list. Similarly, figuring out IOVA address of a memzone is a matter of finding the right memseg list, getting offset and dividing by page size to get the appropriate memseg. This commit also removes rte_eal_dump_physmem_layout() call, according to deprecation notice [1], and removes that deprecation notice as well. On 32-bit targets due to limited VA space, DPDK will no longer spread memory to different sockets like before. Instead, it will (by default) allocate all of the memory on socket where master lcore is. To override this behavior, --socket-mem must be used. The rest of the changes are really ripple effects from the memseg change - heap changes, compile fixes, and rewrites to support fbarray-backed memseg lists. Due to earlier switch to _walk() functions, most of the changes are simple fixes, however some of the _walk() calls were switched to memseg list walk, where it made sense to do so. Additionally, we are also switching locks from flock() to fcntl(). Down the line, we will be introducing single-file segments option, and we cannot use flock() locks to lock parts of the file. Therefore, we will use fcntl() locks for legacy mem as well, in case someone is unfortunate enough to accidentally start legacy mem primary process alongside an already working non-legacy mem-based primary process. [1] http://dpdk.org/dev/patchwork/patch/34002/ Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Tested-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
2018-04-11 12:30:24 +00:00
rte_memseg_list_walk;
mem: add function to walk all memsegs For code that might need to iterate over list of allocated segments, using this API will make it more resilient to internal API changes and will prevent copying the same iteration code over and over again. Additionally, down the line there will be locking implemented, so users of this API will not need to care about locking either. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Tested-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
2018-04-11 12:30:00 +00:00
rte_memseg_walk;
eal: add channel for multi-process communication Previouly, there are three channels for multi-process (i.e., primary/secondary) communication. 1. Config-file based channel, in which, the primary process writes info into a pre-defined config file, and the secondary process reads the info out. 2. vfio submodule has its own channel based on unix socket for the secondary process to get container fd and group fd from the primary process. 3. pdump submodule also has its own channel based on unix socket for packet dump. It'd be good to have a generic communication channel for multi-process communication to accommodate the requirements including: a. Secondary wants to send info to primary, for example, secondary would like to send request (about some specific vdev to primary). b. Sending info at any time, instead of just initialization time. c. Share FDs with the other side, for vdev like vhost, related FDs (memory region, kick) should be shared. d. A send message request needs the other side to response immediately. This patch proposes to create a communication channel, based on datagram unix socket, for above requirements. Each process will block on a unix socket waiting for messages from the peers. Three new APIs are added: 1. rte_eal_mp_action_register() is used to register an action, indexed by a string, when a component at receiver side would like to response the messages from the peer processe. 2. rte_eal_mp_action_unregister() is used to unregister the action if the calling component does not want to response the messages. 3. rte_eal_mp_sendmsg() is used to send a message, and returns immediately. If there are n secondary processes, the primary process will send n messages. Suggested-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com> Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2018-01-30 06:58:08 +00:00
rte_mp_action_register;
rte_mp_action_unregister;
eal: add synchronous multi-process communication We need the synchronous way for multi-process communication, i.e., blockingly waiting for reply message when we send a request to the peer process. We add two APIs rte_eal_mp_request() and rte_eal_mp_reply() for such use case. By invoking rte_eal_mp_request(), a request message is sent out, and then it waits there for a reply message. The caller can specify the timeout. And the response messages will be collected and returned so that the caller can decide how to translate them. The API rte_eal_mp_reply() is always called by an mp action handler. Here we add another parameter for rte_eal_mp_t so that the action handler knows which peer address to reply. sender-process receiver-process ---------------------- ---------------- thread-n |_rte_eal_mp_request() ----------> mp-thread |_timedwait() |_process_msg() |_action() |_rte_eal_mp_reply() mp_thread <---------------------| |_process_msg() |_signal(send_thread) thread-m <----------| |_collect-reply * A secondary process is only allowed to talk to the primary process. * If there are multiple secondary processes for the primary process, it will send request to peer1, collect response from peer1; then send request to peer2, collect response from peer2, and so on. * When thread-n is sending request, thread-m of that process can send request at the same time. * For pair <action_name, peer>, we guarantee that only one such request is on the fly. Suggested-by: Anatoly Burakov <anatoly.burakov@intel.com> Suggested-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com> Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2018-01-30 06:58:09 +00:00
rte_mp_reply;
eal: rename IPC request as synchronous one Rename rte_mp_request to rte_mp_request_sync to indicate that this request will be done synchronously (as opposed to asynchronous request, which comes in next patch). Also, fix alphabetical ordering for .map file. Suggested-by: Thomas Monjalon <thomas@monjalon.net> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Jianfeng Tan <jianfeng.tan@intel.com>
2018-03-31 17:06:15 +00:00
rte_mp_request_sync;
eal: add IPC asynchronous request This API is similar to the blocking API that is already present, but reply will be received in a separate callback by the caller (callback specified at the time of request, rather than registering for it in advance). Under the hood, we create a separate thread to deal with replies to asynchronous requests, that will just wait to be notified by the main thread, or woken up on a timer. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Jianfeng Tan <jianfeng.tan@intel.com>
2018-03-31 17:06:16 +00:00
rte_mp_request_async;
eal: rename IPC request as synchronous one Rename rte_mp_request to rte_mp_request_sync to indicate that this request will be done synchronously (as opposed to asynchronous request, which comes in next patch). Also, fix alphabetical ordering for .map file. Suggested-by: Thomas Monjalon <thomas@monjalon.net> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Jianfeng Tan <jianfeng.tan@intel.com>
2018-03-31 17:06:15 +00:00
rte_mp_sendmsg;
service: add attribute get function This commit adds a new function to the service API to allow the application to retrieve items about each individual service in the system. A unit test checks the return values of a variety of invalid and valid calls. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
2018-01-12 10:27:16 +00:00
rte_service_attr_get;
service: add reset all attributes for service This commit introduces a new API, allowing the application to reset attributes of a service like the cycle count. Given this functionality is now exposed to the user, remove the resetting of stats during a dump() call. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
2018-01-12 10:27:17 +00:00
rte_service_attr_reset_all;
service: return integer service id from register This commit reworks the service register function to accept an extra parameter. The parameter is a uint32_t *, which when provided will be set to the integer service_id that the newly registered service is represented by. This is useful for services that wish to validate settings at a later point in time - they need to know their own service id. This commit updates the eventdev sw pmd, as well as unit tests to use the new register API. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
2017-08-21 12:58:04 +00:00
rte_service_component_register;
service: use id in unregister This commit reworks the unregister API to accept an integer. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
2017-08-21 12:58:07 +00:00
rte_service_component_unregister;
service: add component runstate This commit adds a new flag that the component (or "backend") can use to indicate readyness. The service function callback will not be called until the component sets itself as ready. The use-case behind adding this feature is eg: a service that requires configuration before it can start. Any service that emulates an ethdev will have rte_eth_dev_configure() called, and only after that the service will know how many queues/etc to allocate. Once that configuration is complete, the service marks itself as ready using rte_service_component_runstate_set(). This feature request results from prototyping services, and requiring a flag in each service to note "internal" readyness. Instead that logic is now lifted to the service library. The unit tests have been updated to test the component runstate. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
2017-08-21 12:58:14 +00:00
rte_service_component_runstate_set;
service: introduce service cores concept Add header files, update .map files with new service functions, and add the service header to the doxygen for building. This service header API allows DPDK to use services as a concept of something that requires CPU cycles. An example is a PMD that runs in software to schedule events, where a hardware version exists that does not require a CPU. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-07-11 14:19:27 +00:00
rte_service_dump;
service: fix memory leak with new function The rte_service_finalize routine checks if service is initialized or not. If yes; releases internal memory for services and lcore states are freed. This routine is to be invoked at end of application termination. Fixes: 21698354c832 ("service: introduce service cores concept") Cc: stable@dpdk.org Signed-off-by: Vipin Varghese <vipin.varghese@intel.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
2018-01-26 20:55:36 +00:00
rte_service_finalize;
service: introduce service cores concept Add header files, update .map files with new service functions, and add the service header to the doxygen for building. This service header API allows DPDK to use services as a concept of something that requires CPU cycles. An example is a PMD that runs in software to schedule events, where a hardware version exists that does not require a CPU. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-07-11 14:19:27 +00:00
rte_service_get_by_id;
rte_service_get_by_name;
rte_service_get_count;
service: use id in get by name function This commit reworks the service_get_by_name() function to accept an integer, and removes the service_get_by_id() function. All functions now accept an integer argument representing the service, so it is no longer required to expose the service_spec pointers to the application. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
2017-08-21 12:58:08 +00:00
rte_service_get_name;
service: introduce service cores concept Add header files, update .map files with new service functions, and add the service header to the doxygen for building. This service header API allows DPDK to use services as a concept of something that requires CPU cycles. An example is a PMD that runs in software to schedule events, where a hardware version exists that does not require a CPU. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-07-11 14:19:27 +00:00
rte_service_lcore_add;
rte_service_lcore_count;
service: add count per lcore This new API returns the number of services that are running on a specific service core. It allows an application to decide which service core to run a new service on. Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
2017-08-29 12:32:51 +00:00
rte_service_lcore_count_services;
service: introduce service cores concept Add header files, update .map files with new service functions, and add the service header to the doxygen for building. This service header API allows DPDK to use services as a concept of something that requires CPU cycles. An example is a PMD that runs in software to schedule events, where a hardware version exists that does not require a CPU. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-07-11 14:19:27 +00:00
rte_service_lcore_del;
rte_service_lcore_list;
rte_service_lcore_reset_all;
rte_service_lcore_start;
rte_service_lcore_stop;
service: use id in lcore to service map functions This commit updates the APIs exposed to map service cores and services. The previous APIs required a pointer to a service, and used two separate functions for enable and disable. The new API uses an integer ID for the service and has a parameter for map or unmap. Unit tests are updated and passing, and the map file is updated to the new function names. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
2017-08-21 12:58:03 +00:00
rte_service_map_lcore_get;
rte_service_map_lcore_set;
service: introduce service cores concept Add header files, update .map files with new service functions, and add the service header to the doxygen for building. This service header API allows DPDK to use services as a concept of something that requires CPU cycles. An example is a PMD that runs in software to schedule events, where a hardware version exists that does not require a CPU. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-07-11 14:19:27 +00:00
rte_service_probe_capability;
service: add function to run on app lcore This commit adds a new function which allows an application lcore (aka; *not* a dedicated service-lcore) to run a service. This function is required to allow applications to gradually port functionality to using services, while still being able to run ordinary application functions. This requirement became clear when a patch to the existing eventdev/pipeline sample app was modified to use a service-core for scheduling - and that same core should be capable of running the "worker()" function from the application too. This patch refactors the existing running code into a smaller "service_run" function, which can be called by the dedicated service-core loop, and the newly added function. [1] http://dpdk.org/ml/archives/dev/2017-October/079876.html Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
2017-10-25 13:25:28 +00:00
rte_service_run_iter_on_app_lcore;
service: use id in runstate function This commit reworks the API to move from two separate start and stop functions, to a "runstate" API which allows setting the runstate. The is_running API is replaced with an function to query the runstate. The runstate functions take a id value for service. Unit tests and the eventdev sw pmd are updated. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
2017-08-21 12:58:05 +00:00
rte_service_runstate_get;
rte_service_runstate_set;
service: allow to disable core check This commit adds a new function to disable the runtime mapped service-cores check. This allows an application to take responsibility of running unmapped services. This feature is useful in cases like unit tests, where the application code (or unit test in this case) requires accurate control over when the service function is called to ensure correct behaviour, and when an application has an advanced use-case and wishes to manage services manually. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
2017-10-25 13:25:29 +00:00
rte_service_set_runstate_mapped_check;
service: introduce service cores concept Add header files, update .map files with new service functions, and add the service header to the doxygen for building. This service header API allows DPDK to use services as a concept of something that requires CPU cycles. An example is a PMD that runs in software to schedule events, where a hardware version exists that does not require a CPU. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-07-11 14:19:27 +00:00
rte_service_set_stats_enable;
rte_service_start_with_defaults;
eal: provide API for querying valid socket ids During lcore scan, find all socket ID's and store them, and provide public API to query valid socket id's. This will break the ABI, so bump ABI version. Also, remove deprecation notice corresponding to this change. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
2018-03-31 17:08:13 +00:00
rte_socket_count;
rte_socket_id_by_idx;
vfio: allow to map other memory regions Currently it is not possible to use memory that is not owned by DPDK to perform DMA. This scenarion might be used in vhost applications (like SPDK) where guest send its own memory table. To fill this gap provide API to allow registering arbitrary address in VFIO container. Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Signed-off-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com> Tested-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
2018-04-11 12:30:21 +00:00
rte_vfio_dma_map;
rte_vfio_dma_unmap;
eal: add hotplug add/remove device Signed-off-by: Jan Blunck <jblunck@infradead.org>
2017-06-30 18:19:41 +00:00
eal/x86: get hypervisor name The CPUID instruction is caught by hypervisor which can return a flag indicating one is running, and its name. Suggested-by: Stephen Hemminger <sthemmin@microsoft.com> Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-11-30 21:27:01 +00:00
} DPDK_18.02;
Reference in New Issue Copy Permalink