Home
last modified time | relevance | path

Searched refs:run (Results 1 – 25 of 64) sorted by relevance

123

/spdk/test/unit/lib/thread/thread.c/
H A Dthread_ut.c207 bool run; member
215 poller_ctx->run = true; in poller_run_pause()
229 poller_ctx->run = true; in poller_run_pause_resume_pause()
268 poller_ctx.run = false; in poller_pause()
270 CU_ASSERT_EQUAL(poller_ctx.run, true); in poller_pause()
272 poller_ctx.run = false; in poller_pause()
274 CU_ASSERT_EQUAL(poller_ctx.run, false); in poller_pause()
283 poller_ctx.run = false; in poller_pause()
285 CU_ASSERT_EQUAL(poller_ctx.run, true); in poller_pause()
287 poller_ctx.run in poller_pause()
[all...]
/spdk/test/nvmf/target/
H A Dnvmf_vfio_user.sh47 rm -rf /var/run/vfio-user
66 mkdir -p /var/run/vfio-user
69 mkdir -p /var/run/vfio-user/domain/vfio-user$i/$i
81 test_traddr=/var/run/vfio-user/domain/vfio-user$i/$i
97 rm -rf /var/run/vfio-user
H A Dvfio_user_fuzz.sh16 traddr=/var/run/vfio-user
/spdk/go/rpc/mocks/
H A DIClient.go64 func (_c *IClient_Call_Call) Run(run func(method string, params interface{})) *IClient_Call_Call {
66 run(args[0].(string), args[1].(interface{}))
76 func (_c *IClient_Call_Call) RunAndReturn(run func(string, interface{}) (*client.Response, error)) …
77 _c.Call.Return(run)
/spdk/test/nvme/compliance/
H A Dcompliance.sh16 rm -rf /var/run/vfio-user
29 traddr=/var/run/vfio-user
44 rm -rf /var/run/vfio-user
/spdk/test/app/fuzz/iscsi_fuzz/
H A DREADME.md14 The application will terminate when run time expires (see the -t flag).
24 script for targeted debugging on a subsequent run.
26 At the end of each test run, a summary is printed in the following format:
/spdk/doc/
H A Dgetting_started.md76 This script should be run as root. It only needs to be run once on the
83 To rebind devices back to the kernel, you can run
108 enabled you can run the examples as your regular user. If it doesn't, you'll
109 need to run as a privileged user (root).
H A Dcontainers.md15 There are no SPDK specific changes needed to run an SPDK based application in
43 # run the app
55 `sudo docker run --privileged -v /dev/hugepages:/dev/hugepages hello:1.0`
66 $ sudo docker run --privileged -v //dev//hugepages://dev//hugepages hello:1.0
101 Kata containers use-case [Setup to run SPDK vhost-user devices with Kata Containers and Docker](htt…
H A Ddistributions.md12 used as a base for all the tests run against submitted patches. Below is the
33 Jobs listed below are run on bare-metal systems where version of
H A Dspdk_top.md10 an SPDK application schedules SPDK lightweight threads and pollers to run on the CPU core. Therefor…
18 …mmunicate with the app it is viewing, so it will work only with those that run RPC server and supp…
24 Before running spdk_top you need to run the SPDK application whose performance you want to analyze …
54 thread (with poller name, type, run count and period).
66 * Run count - how many times poller was run.
H A Dspdkcli.md27 spdkcli should be run with the same privileges as SPDK application.
35 It is also possible to use spdkcli to run just a single command,
H A Dshfmt.md23 On the CI pool, the shfmt is run against all the updated .sh files that
25 all .sh present in the staging area when run locally from our pre-commit
39 is run with. Additionally, @ref shfmt_examples has more details on how
H A DREADME.md8 To convert the documentation into HTML run `make` in the `doc`
/spdk/test/nvme/perf/
H A DREADME.md5 The link time optimization (lto) gcc flag allows the linker to run a post-link optimization pass on…
25 #### --run-time
31 Fio will run the specified workload for this amount of time before logging any performance numbers.
48 This option will run multiple fio jobs with varying number of NVMe devices. First it will start with
55 This option will run fio job on specified number of NVMe devices. If set to 'all' then max-disk num…
93 Specifies how many times run each workload. End results are averages of these workloads
/spdk/test/app/fuzz/nvme_fuzz/
H A DREADME.md11 1. The user specified run time expires (see the -t flag).
13 3. The user specified a json file containing operations to run and the fuzzer has received valid co…
23 script for targeted debugging on a subsequent run. See `Debugging` below.
27 At the end of each test run, a summary is printed for each namespace in the following format:
/spdk/scripts/perf/nvmf/
H A DREADME.md3 Scripts contained in this directory are used to run TCP and RDMA benchmark tests,
5 To run the scripts in your environment please follow steps below.
49 ## JSON configuration for test run automation
77 to the Initiator systems each time run_nvmf.py script is run. If the SPDK
142 Used to run set_irq_affinity.sh script.
149 mode: default - run IRQ alignment script with no additional options.
190 test run. Available scripts can be found in the spdk/scripts/bpf directory.
245 - fio_bin - path to custom fio binary, which will be used to run IO.
249 - cpus_allowed - str, list of CPU cores to run fio threads on. Takes precedence
260 configured to run i
[all...]
/spdk/scripts/vagrant/
H A DREADME.md109 -r dry-run
202 After running autotest_setup.sh the `run-autorun.sh` can be used to run `spdk/autorun.sh` on a Fedo…
207 $ spdk/scripts/vagrant/run-autorun.sh -h
208 Usage: scripts/vagrant/run-autorun.sh -d <path_to_spdk_tree> [-h] | [-q] | [-n]
211 -n : Noop - dry-run
215 run-spdk-autotest.sh -d . -q
216 run-spdk-autotest.sh -d /home/vagrant/spdk_repo/spdk
/spdk/docker/
H A DREADME.md72 docker-compose run traffic-generator-nvme
73 docker-compose run traffic-generator-virtio
81 docker-compose run -e FIO_ARGS="--minimal" traffic-generator-nvme
104 In order to see data change, once all of the 3 containers are brought up, use `docker-compose run t…
115 - If you run docker < 20.10 under distro which switched fully to cgroups2
/spdk/test/nvmf/
H A DREADME.md3 The test scripts in this directory hierarchy can be run in isolation by passing
/spdk/scripts/
H A Dsma.py122 def run(agent): function
154 run(agent)
H A Dsetup.sh297 The binding process may go faster if you first run this script with
298 DRIVER_OVERRIDE="none" to unbind only the NVMe SSDs, and then run
442 dirs_to_clean=({/var/run,/tmp}/dpdk/spdk{,_pid}+([0-9]))
588 able to use with DPDK and VFIO if run as user "$TARGET_USER".
595 echo "if run as user \"$TARGET_USER\"."
637 rm -f /run/.spdk*
/spdk/app/spdk_top/
H A DREADME34 To run spdk_top:
50 depend on which tab is currently selected. All time and run counter
/spdk/
H A DREADME.md122 Before running `setup.sh`, run `modprobe vfio-pci`
163 installation, run configure with the --with-dpdk option. For example:
200 - run ldconfig specifying the directory containing SPDK shared libraries
221 This script should be run as root.
235 setup.sh for advanced users. To see the full list, run:
267 with no arguments to see the help output. You'll likely need to run the examples
/spdk/test/common/
H A Dskipped_tests.txt25 # These tests are currently only run manually
/spdk/scripts/perf/pm/
H A Dcollect-cpu-load19 -c - Execute count times. 0 is the default and it means to run

123