eal/bsd: rename bsdapp to freebsd

The term "bsdapp" is a legacy one, but just calling the subdirectory
"freebsd" is just clearer for all concerned.

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
This commit is contained in:
Bruce Richardson 2019-03-06 16:22:37 +00:00 committed by Thomas Monjalon
parent 610e235a11
commit 25c99fbd68
22 changed files with 9 additions and 9 deletions

View File

@ -113,7 +113,7 @@ F: doc/guides/prog_guide/ext_app_lib_make_help.rst
Meson build
M: Bruce Richardson <bruce.richardson@intel.com>
F: meson.build
F: lib/librte_eal/bsdapp/BSDmakefile.meson
F: lib/librte_eal/freebsd/BSDmakefile.meson
F: meson_options.txt
F: config/rte_config.h
F: buildtools/gen-pmdinfo-cfile.sh
@ -174,7 +174,7 @@ F: lib/librte_eal/common/eal_common_fbarray.c
F: lib/librte_eal/common/eal_common_mem*
F: lib/librte_eal/common/eal_hugepages.h
F: lib/librte_eal/linuxapp/eal/eal_mem*
F: lib/librte_eal/bsdapp/eal/eal_mem*
F: lib/librte_eal/freebsd/eal/eal_mem*
F: doc/guides/prog_guide/env_abstraction_layer.rst
F: app/test/test_external_mem.c
F: app/test/test_func_reentrancy.c
@ -260,8 +260,8 @@ F: drivers/bus/pci/linux/*vfio*
FreeBSD EAL (with overlaps)
M: Bruce Richardson <bruce.richardson@intel.com>
F: lib/librte_eal/bsdapp/Makefile
F: lib/librte_eal/bsdapp/eal/
F: lib/librte_eal/freebsd/Makefile
F: lib/librte_eal/freebsd/eal/
F: doc/guides/freebsd_gsg/
FreeBSD contigmem

View File

@ -72,7 +72,7 @@ linux_sources()
bsd_sources()
{
find_sources "lib/librte_eal/bsdapp" '*.[chS]'
find_sources "lib/librte_eal/freebsd" '*.[chS]'
}
arm_common()

View File

@ -349,7 +349,7 @@ EAL provides the event APIs for this event-driven thread mode.
Taking linuxapp as an example, the implementation relies on epoll. Each thread can monitor an epoll instance
in which all the wake-up events' file descriptors are added. The event file descriptors are created and mapped to
the interrupt vectors according to the UIO/VFIO spec.
From bsdapp's perspective, kqueue is the alternative way, but not implemented yet.
From FreeBSD's perspective, kqueue is the alternative way, but not implemented yet.
EAL initializes the mapping between event file descriptors and interrupt vectors, while each device initializes the mapping
between interrupt vectors and queues. In this way, EAL actually is unaware of the interrupt cause on the specific vector.

View File

@ -6,7 +6,7 @@ include $(RTE_SDK)/mk/rte.vars.mk
DIRS-y += common
DIRS-$(CONFIG_RTE_EXEC_ENV_LINUXAPP) += linuxapp
DEPDIRS-linuxapp := common
DIRS-$(CONFIG_RTE_EXEC_ENV_BSDAPP) += bsdapp
DEPDIRS-bsdapp := common
DIRS-$(CONFIG_RTE_EXEC_ENV_BSDAPP) += freebsd
DEPDIRS-freebsd := common
include $(RTE_SDK)/mk/rte.subdir.mk

View File

@ -15,7 +15,7 @@ if host_machine.system() == 'linux'
elif host_machine.system() == 'freebsd'
dpdk_conf.set('RTE_EXEC_ENV_BSDAPP', 1)
subdir('bsdapp/eal')
subdir('freebsd/eal')
else
error('unsupported system type "@0@"'.format(host_machine.system()))