numam-spdk/test/external_code
Seth Howell c89b28a9eb test/external: Add setup call to test_make.sh
This makes sure that we will have the hugepages we need
even on systems that don't have them configured by default.

Signed-off-by: Seth Howell <seth.howell@intel.com>
Change-Id: I9a0d82e0abf6363c1c037732b543c05e8931f97e
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2141
Community-CI: Mellanox Build Bot
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Paul Luse <paul.e.luse@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2020-05-05 08:03:48 +00:00
..
hello_world test/autobuild: verify external code can link to libs 2020-04-15 22:10:08 +00:00
passthru test/autobuild: verify external code can link to libs 2020-04-15 22:10:08 +00:00
Makefile test/autobuild: verify external code can link to libs 2020-04-15 22:10:08 +00:00
README.md test/autobuild: verify external code can link to libs 2020-04-15 22:10:08 +00:00
test_make.sh test/external: Add setup call to test_make.sh 2020-05-05 08:03:48 +00:00

This directory is meant to demonstrate how to link an external application and bdev module to the SPDK libraries. The makefiles contain six examples of linking against spdk libraries. They cover linking an application both with and without a custom bdev. For each of these categories, they also demonstrate linking against the spdk combined shared library, individual shared libraries, and static libraries.

This directory also contains a convenient test script, test_make.sh, which automates making SPDK and testing all six of these linker options. It takes a single argument, the path to an SPDK repository and should be run as follows:

sudo ./test_make.sh /path/to/spdk

The application hello_world and bdev module passthru_external have been copied from their namesakes in the top level SPDK github repository and don't have any special functionality.