Home
last modified time | relevance | path

Searched refs:directory (Results 1 – 25 of 35) sorted by relevance

12

/spdk/test/external_code/
H A DMakefile57 $(MAKE) --directory=hello_world bdev_shared_combo
60 $(MAKE) --directory=hello_world bdev_shared_iso
63 $(MAKE) --directory=hello_world alone_shared_combo
66 $(MAKE) --directory=hello_world alone_shared_iso
69 $(MAKE) --directory=hello_world bdev_static
72 $(MAKE) --directory=hello_world alone_static
75 $(MAKE) --directory=accel shared_module
78 $(MAKE) --directory=accel shared_driver
81 $(MAKE) --directory=accel static_module
84 $(MAKE) --directory=accel static_driver
[all …]
H A DREADME.md1 This directory is meant to demonstrate how to link an external application and bdev
7 This directory also contains a convenient test script, test_make.sh, which automates making SPDK
/spdk/doc/
H A Doverview.md32 The `app` top-level directory contains full-fledged applications, built out of the SPDK
41 The `lib` directory contains the real heart of SPDK. Each component is a C library with
42 its own directory under `lib`. Some of the key libraries are:
49 The `doc` top-level directory contains all of SPDK's documentation. API Documentation
51 explanations reside in this directory, as well as the Doxygen config file.
53 To build the documentation, just type `make` within the doc directory.
57 The `examples` top-level directory contains a set of examples intended to be used
68 The `include` directory is where all of the header files are located. The public API
71 directory and include the headers by prefixing `spdk/` like this:
77 Most of the headers here correspond with a library in the `lib` directory. There
[all …]
H A Dlibraries.md14 The SPDK libraries are divided into two directories. The `lib` directory contains the base librarie…
16 modules and are located in the `module` directory. For example, the `spdk_sock` library is containe…
17 `lib` directory while the implementations of socket abstractions, `sock_posix` and `sock_uring`
18 are contained in the `module` directory.
22 The libraries in the `lib` directory can be readily divided into four categories:
39 The one library in the `lib` directory that doesn't fit into the above classification is the `spdk_…
44 Currently there are two exceptions in the `lib` directory which still rely on `spdk_event`, `spdk_v…
53 The component libraries in the `module` directory represent specific implementations of the base li…
54 the `lib` directory. As with the `lib` directory, much care has been taken to avoid dependencies on…
57 There are seven sub-directories in the `module` directory which each hold a different class of libr…
[all …]
H A Dgdb_macros.md180 the destination directory to the PYTHONPATH. This is not mandatory, and can be
185 In the example below, I copied the macros to the /tmp directory which is not in
186 the PYTHONPATH, so I had to manually add the directory to the path.
199 On most systems, the data directory is /usr/share/gdb. The python script should
200 be copied into the python/gdb/function (or python/gdb/command) directory under
201 the data directory, e.g. /usr/share/gdb/python/gdb/function.
H A Dblobfs.md16 Clone the RocksDB repository from the SPDK GitHub fork into a separate directory.
89 * BlobFS currently supports only a flat namespace for files with no directory support. Filenames a…
91 underway which will be the underpinning for BlobFS directory support in a future release.
H A DREADME.md9 directory. The output will be located in `doc/output/html`. Before
H A Dstylesheet.css680 div.directory {
687 .directory table {
691 .directory td {
697 .directory td.entry {
703 .directory td.entry a {
707 .directory td.entry a img {
711 .directory td.desc {
719 .directory tr.even {
724 .directory img {
728 .directory .levels {
[all …]
H A Dgetting_started.md105 Example code is located in the examples directory. The examples are compiled
115 directory. This includes the [iSCSI target](https://spdk.io/doc/iscsi.html)
H A Dbackporting.md63 ### 1. Enter SPDK directory and update master branch
69 ### 2. Enter DPDK submodule directory and update it
H A Dvagrant.md29 Basically, the script will create a new sub-directory based on distribution you choose,
61 mkdir: created directory '/home/user/spdk/scripts/vagrant/ubuntu18'
H A Drpm.md42 By default, all RPM packages should be created under $HOME directory of the
/spdk/test/dd/
H A Dposix.sh30 directory() { function
31 NOT "${DD_APP[@]}" --if="$test_file0" --iflag=directory --of="$test_file0"
32 NOT "${DD_APP[@]}" --if="$test_file0" --of="$test_file0" --oflag=directory
103 run_test "dd_flag_directory" directory
115 run_test "dd_flag_directory_forced_aio" directory
/spdk/scripts/env_dpdk/
H A DREADME.md37 Filename for any patch within that directory should start with first DPDK version
42 If API was changed, a new directory should be created `spdk_root/lib/env_dpdk/<ver>`
46 Not every DPDK version requires new directory.
/spdk/scripts/vagrant/
H A DREADME.md106 --vhost-host-dir=<path> directory path with vhost test dependencies
108 --vhost-vm-dir=<path> directory where to put vhost dependencies in VM
124 Call this script from a parent directory. This will allow the creation of multiple VMs in separate
134 2. copy the needed files from `spdk/scripts/vagrant/` into the <distro> directory
135 3. create a working virtual box in the <distro> directory
138 6. rsync a copy of the `~/vagrant_tools` directory to `/home/vagrant/tools` (optional)
141 This arrangement allows the provisioning of multiple, different VMs within that same directory hier…
151 A copy of the `spdk` repository you cloned will exist in the `spdk_repo` directory of the `/home/va…
H A Drun-autorun.sh215 echo Output directory: ${GIT_REPO_PATH}
H A DVagrantfile77 return unless File.directory?(File.expand_path(src_path))
92 next unless File.directory?(File.expand_path(src_path))
317 # and to be able to run vagrant from user $HOME directory
/spdk/test/nvmf/
H A DREADME.md3 The test scripts in this directory hierarchy can be run in isolation by passing
/spdk/scripts/perf/nvmf/
H A DREADME.md3 Scripts contained in this directory are used to run TCP and RDMA benchmark tests,
27 to /usr/src/local directory in order to configure NIC ports IRQ affinity.
28 If custom directory is to be used, then it must be set using irq_scripts_dir
141 - irq_scripts_dir - path to scripts directory of Mellanox mlnx-tools package;
190 test run. Available scripts can be found in the spdk/scripts/bpf directory.
246 Additionally, the directory where the binary is located should also contain
266 - irq_scripts_dir - path to scripts directory of Mellanox mlnx-tools package;
438 directory. You can specify a different configuration file at runtime as below:
447 `spdk/scripts` directory.
453 Results directory pat
[all...]
/spdk/test/fuzz/
H A Dllvm.sh
/spdk/test/common/config/
H A DREADME.md1 Scripts contained in this directory, and the pkgdep/, will attempt to provision
/spdk/test/common/
H A Dautobuild_common.sh77 echo "DPDK directory does not exist at the provided location."
205 # Sanitize ownership of the target directory post sudo above
332 $MAKE -C "$rootdir"/doc --no-print-directory $MAKEFLAGS Q=@ &> "$out"/doxygen.log
350 $MAKE -C "$rootdir"/doc/output/latex --no-print-directory $MAKEFLAGS &>> "$out"/doxygen.log
359 $MAKE -C "$rootdir"/doc --no-print-directory $MAKEFLAGS clean &>> "$out"/doxygen.log
H A Dskipped_build_files.txt40 # These files are in the external_code directory which doesn't get compiled with SPDK.
/spdk/
H A DREADME.md200 - run ldconfig specifying the directory containing SPDK shared libraries
245 `spdk/build/bin` directory:
265 Example code is located in the examples directory. The examples are compiled
/spdk/scripts/perf/pm/
H A Dcollect-cpu-temp230 output will be dumped to /tmp or directory set by -d.

12