bdevperf: introduce params to "perform_tests" RPC

allow users to configure the test run using the "perform_tests" RPC

Change-Id: Ie246832f94adce3d8813fd4792b7ea86ab528a60
Signed-off-by: Eugene Koby

bdevperf: introduce params to "perform_tests" RPC

allow users to configure the test run using the "perform_tests" RPC

Change-Id: Ie246832f94adce3d8813fd4792b7ea86ab528a60
Signed-off-by: Eugene Kobyak <eugene.kobyak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20978
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Jim Harris <jim.harris@samsung.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>

show more ...

bdevperf: add logging for bdevperf jobs

Change-Id: I2a332f634ce14713c8bd2478305d42b04b195b48
Signed-off-by: Eugene Kobyak <eugene.kobyak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/

bdevperf: add logging for bdevperf jobs

Change-Id: I2a332f634ce14713c8bd2478305d42b04b195b48
Signed-off-by: Eugene Kobyak <eugene.kobyak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/21445
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Jim Harris <jim.harris@samsung.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>

show more ...

bdevperf: make verify_test_params() reusable

remove spdk_app_opts from verify_test_params() to allow future patches
to reuse this function when getting parameters from RPC

Change-Id: If235d08cfeddf

bdevperf: make verify_test_params() reusable

remove spdk_app_opts from verify_test_params() to allow future patches
to reuse this function when getting parameters from RPC

Change-Id: If235d08cfeddf7e730a3759f2ffe46c55552a28d
Signed-off-by: Eugene Kobyak <eugene.kobyak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/21033
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Jim Harris <jim.harris@samsung.com>

show more ...

bdevperf: add option to generate unique writes (-U)

By default, write I/O uses empty (all zero) buffers, only verify writes
generate some non-zero data but the pattern is repeatable. This new
option

bdevperf: add option to generate unique writes (-U)

By default, write I/O uses empty (all zero) buffers, only verify writes
generate some non-zero data but the pattern is repeatable. This new
option enables writing different data for each I/O, based on a job's I/O
counter. This is useful for testing bdevs, e.g. when we need to compare
data after overwriting some blocks multiple times.

Change-Id: I36e9f783885b519a159a6dad603b370caf59778b
Signed-off-by: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20700
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Jim Harris <jim.harris@samsung.com>

show more ...

bdevperf: better explain -z option

Specify that this waits specifically for the perform_tests RPC, and point
users to the script that enables it.

Signed-off-by: Jim Harris <jim.harris@samsung.com>

bdevperf: better explain -z option

Specify that this waits specifically for the perform_tests RPC, and point
users to the script that enables it.

Signed-off-by: Jim Harris <jim.harris@samsung.com>
Change-Id: I98838a2a286c17345e89b7f7e72d97d89c2e9257
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/21382
Community-CI: Mellanox Build Bot
Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com>
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>

show more ...

bdevperf: fix argument parser function to use 'arg', not 'optarg'

Change-Id: I1491fb239a3d964b4cb46e20b8c226e3e6a9aa1d
Signed-off-by: Eugene Kobyak <eugene.kobyak@intel.com>
Reviewed-on: https://rev

bdevperf: fix argument parser function to use 'arg', not 'optarg'

Change-Id: I1491fb239a3d964b4cb46e20b8c226e3e6a9aa1d
Signed-off-by: Eugene Kobyak <eugene.kobyak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/21306
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Jim Harris <jim.harris@samsung.com>
Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com>
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>

show more ...

bdevperf: accept unit suffixes when specifying IO size

It's now possible to specify IO size as 4k or 128k instead of 4096,
131072.

Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com>
Change-Id

bdevperf: accept unit suffixes when specifying IO size

It's now possible to specify IO size as 4k or 128k instead of 4096,
131072.

Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com>
Change-Id: Ia60c12cdd9d30cc835f87fc5f2c2c5a47ce03d6c
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20579
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Jim Harris <jim.harris@samsung.com>

show more ...

bdevperf: free job configs at the end of test run

It makes it to possible to use different bdevs on subsequent
"perform_tests" runs, as the bdev will now be selected just before
running the tests an

bdevperf: free job configs at the end of test run

It makes it to possible to use different bdevs on subsequent
"perform_tests" runs, as the bdev will now be selected just before
running the tests and not at the start of the application.

This can be useful, when the first set of tests are supposed to be run
on one bdev, but then switch to another one without having to restart
the application. E.g.:

$ build/examples/bdevperf -z -t 8 -w randread -q 128 -o 4096 &
$ scripts/rpc.py bdev_null_create null0 100 4096
$ examples/bdev/bdevperf/bdevperf.py perform_tests

Running I/O for 8 seconds...

Latency(us)
Device Information : runtime(s) IOPS MiB/s Fail/s TO/s Average min max
Job: null0 (Core Mask 0x1)
null0 : 8.00 410608.08 1603.94 0.00 0.00 310.09 117.19 2066.20
===================================================================================================================
Total : 410608.08 1603.94 0.00 0.00 310.09 117.19 2066.20

$ scripts/rpc.py bdev_passthru_create -b null0 -p passthru0
$ examples/bdev/bdevperf/bdevperf.py perform_tests

Running I/O for 8 seconds...

Latency(us)
Device Information : runtime(s) IOPS MiB/s Fail/s TO/s Average min max
Job: passthru0 (Core Mask 0x1)
passthru0 : 8.00 186112.27 727.00 0.00 0.00 685.95 208.21 2876.30
===================================================================================================================
Total : 186112.27 727.00 0.00 0.00 685.95 0.00 2876.30

Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com>
Change-Id: I720d476eed135c0c12dacd2455c0e08fb6c51ecd
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20419
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Jim Harris <jim.harris@samsung.com>

show more ...

bdevperf: allocate lcore threads when creating jobs

Previously, lcore threads were allocated when creating job configs,
which is done only once at startup, but are freed when the test is
finished in

bdevperf: allocate lcore threads when creating jobs

Previously, lcore threads were allocated when creating job configs,
which is done only once at startup, but are freed when the test is
finished in bdevperf_test_done(), which would lead to a segfault when
bdevperf was started with the `-z` option and the `perform_tests` RPC
was sent more than once.

Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com>
Change-Id: I627c97d505cda6faf530117c0daeea0fe7254094
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20270
Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com>
Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com>
Community-CI: Mellanox Build Bot
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>

show more ...

bdevperf: add missing write_zeroes pattern to pattern types

Signed-off-by: Amir Haroush <amir.haroush@huawei.com>
Signed-off-by: Shai Fultheim <shai.fultheim@huawei.com>
Change-Id: I15fa7f5da869d12d

bdevperf: add missing write_zeroes pattern to pattern types

Signed-off-by: Amir Haroush <amir.haroush@huawei.com>
Signed-off-by: Shai Fultheim <shai.fultheim@huawei.com>
Change-Id: I15fa7f5da869d12d2816a3c7164d291c28cf0b6f
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20103
Reviewed-by: Jim Harris <jim.harris@samsung.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Community-CI: Mellanox Build Bot
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>

show more ...

bdevperf: fixed memory 'double free'

Fixed issue detected by Coverity scan. The memory
allocated for 'config' structure could be freed
twice in some cases.
Now, when a memory for 'config ' is freed,

bdevperf: fixed memory 'double free'

Fixed issue detected by Coverity scan. The memory
allocated for 'config' structure could be freed
twice in some cases.
Now, when a memory for 'config ' is freed, the pointer
is set to NULL. If free(config) will be called second time,
it will take no action.

Change-Id: I1bd3f8b17503feae5975afbae9d96ad6ce19b67e
Signed-off-by: Marcin Spiewak <marcin.spiewak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/19974
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>

show more ...

bdevperf: Use RPC log file by opening a user specified file

RPC log file is available for SPDK applications. bdevperf is a good
candidate to use the RPC log file.

Signed-off-by: Shuhei Matsumoto <s

bdevperf: Use RPC log file by opening a user specified file

RPC log file is available for SPDK applications. bdevperf is a good
candidate to use the RPC log file.

Signed-off-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Change-Id: Ic6ffb044080524761330d7420b25ccec293bd817
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/18912
Community-CI: Mellanox Build Bot
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>

show more ...

bdevperf: Add bdevperf_fini() and move free_job_config() into it

We want to close a log file for JSON RPC calls for the bdevperf
application. To do it simply, add bdevperf_fini() and move
free_job_c

bdevperf: Add bdevperf_fini() and move free_job_config() into it

We want to close a log file for JSON RPC calls for the bdevperf
application. To do it simply, add bdevperf_fini() and move
free_job_config() into it.

Signed-off-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Change-Id: Ic464ab79e1e88d243a54e2c8862c04ea895ea202
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/18911
Reviewed-by: Jim Harris <jim.harris@gmail.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>

show more ...

dif: remove packed attribute from spdk_dif_ctx_init_ext_opts

Following the recommendation introduced in 1d77eec82, the packed
attribute was removed from spdk_dif_ctx_init_ext_opts and the way its
si

dif: remove packed attribute from spdk_dif_ctx_init_ext_opts

Following the recommendation introduced in 1d77eec82, the packed
attribute was removed from spdk_dif_ctx_init_ext_opts and the way its
size is calculated was changed to use SPDK_SIZEOF().

Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com>
Change-Id: I8dab3ee5afcd2afe803dacc563bee9b029c7cbf6
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/18597
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Community-CI: Mellanox Build Bot

show more ...

lib/util/dif: Add an ext_opts param to spdk_dif_ctx_init

The extended options structure for the dif context
initialization allows for adding new arguments
without the function signature change. The

lib/util/dif: Add an ext_opts param to spdk_dif_ctx_init

The extended options structure for the dif context
initialization allows for adding new arguments
without the function signature change. The first
extended parameter is the DIF Protection Information
format (CRC-16).

Change-Id: I6a32e8570676265d757fc7251441e5547bbb475d
Signed-off-by: Slawomir Ptak <slawomir.ptak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/18146
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Mellanox Build Bot

show more ...

bdevperf: avoid using of out of boundary indices

This patch corrects patch 17176, which doesn't
corectly addresses issue found by Klocwork scan.
Both indices, k and i, needs to be verified here,
as

bdevperf: avoid using of out of boundary indices

This patch corrects patch 17176, which doesn't
corectly addresses issue found by Klocwork scan.
Both indices, k and i, needs to be verified here,
as both *filename and *out has limited size.
As the 'k' index is incremented inside the loop,
the loop entry condition for k index must be set to
k < (BDEVPERF_CONFIG_MAX_FILENAME - 1) not to
k < BDEVPERF_CONFIG_MAX_FILENAME,
to avoid situation where i and k are both equal to
BDEVPERF_CONFIG_MAX_FILENAME - 1, 'for' loop pass
is therefore executed, and inside the loop k is
incremented (so it is set to
k=BDEVPERF_CONFIG_MAX_FILENAME) giving in result
out of boundary index for *out table in line:
out[k] = 0;

Change-Id: Idf62c40f86f3aa4c8c6372bc74e94703925de47e
Signed-off-by: Marcin Spiewak <marcin.spiewak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/18135
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Mellanox Build Bot

show more ...

bdevperf: avoid writing outside "out" array boundary

Currently variables "i" and "k" in config_filename_next()
function may increase at the same speed. When repeating
"for" loop at line 1862 both "i

bdevperf: avoid writing outside "out" array boundary

Currently variables "i" and "k" in config_filename_next()
function may increase at the same speed. When repeating
"for" loop at line 1862 both "i" and "k" are being incremented:
+ i by the for loop,
+ k by the "out[k++]" instruction.
This means that there may be a case, where for loop ends with
"i < BDEVPERF_CONFIG_MAX_FILENAME" condition, as value of "i"
is equal to BDEVPERF_CONFIG_MAX_FILENAME, and at the same time
value of "k" is also equal to BDEVPERF_CONFIG_MAX_FILENAME,
because after writing to out[BDEVPERF_CONFIG_MAX_FILENAME - 1]
element, we increment it one last time.
This results in writing "0" value at line 1873 to memory outside
"out" array boundary.
To amend this problem, compare k against
BDEVPERF_CONFIG_MAX_FILENAME, insted of i.

Change-Id: Ia45778c1f267d2b9dcd676cd9b6c662d09f6f94e
Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/17176
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>

show more ...

bdevperf: free job->zipf

Currently we do not free the memory allocated
during spdk_zipf_create() call, when we exit
the for loop on line 1769 with error. Remedy
this problem by adding spdk_zipf_free

bdevperf: free job->zipf

Currently we do not free the memory allocated
during spdk_zipf_create() call, when we exit
the for loop on line 1769 with error. Remedy
this problem by adding spdk_zipf_free() calls.

Change-Id: I1d593ad2375204b158a2c97b23e492e69f836f43
Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/17405
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Community-CI: Mellanox Build Bot
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com>

show more ...

bdevperf: Create and use per lcore thread pool

If bdevperf runs with -C option and two or more NVMe bdevs,
two or more poll groups are created on each CPU core because bdevperf
creates one SPDK thre

bdevperf: Create and use per lcore thread pool

If bdevperf runs with -C option and two or more NVMe bdevs,
two or more poll groups are created on each CPU core because bdevperf
creates one SPDK thread per job per CPU core in this case.

However, generally SPDK application creates one SPDK thread per CPU
core. We want bdevperf to immitate closely generic SPDK application
pattern.

For this requirement, create a thread poll made of per core threads.
Then, each job gets one of the threads whose lcore matches instead of
creating a new thread.

This feature is available only if bdevperf's config file is not used
because bdevperf's config file can specify cpumap per job.

Fixes issue #2933

Signed-off-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Change-Id: I0bd5a72f9ee8deade6c4e8ca0cdea3c89ff2541f
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16994
Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>

show more ...

bdevperf: Use job->name instead of spdk_thread_get_name(job->thread)

The next patch will support a feature to share per lcore thread among
multiple jobs. Hence, spdk_thread_get_name(job->thread) wil

bdevperf: Use job->name instead of spdk_thread_get_name(job->thread)

The next patch will support a feature to share per lcore thread among
multiple jobs. Hence, spdk_thread_get_name(job->thread) will not be
usable. Currently job->name is equal with
spdk_thread_get_name(job->thread). Hence, we can do this replacement
simply.

Signed-off-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Change-Id: I9e086d18043cf6125e059c85044420138c0eeece
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16993
Community-CI: Mellanox Build Bot
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>

show more ...

bdevperf: Random map for picking I/O offsets

Added a random map feature (-D command line option),
which enables offset tracking of every I/O
for random read, random write and random rw mix,
to make

bdevperf: Random map for picking I/O offsets

Added a random map feature (-D command line option),
which enables offset tracking of every I/O
for random read, random write and random rw mix,
to make sure every offset is accessed the same
number of times.

Change-Id: I5a0a23718b9f0a94ca094f86175c036b3230fb8b
Signed-off-by: Slawomir Ptak <slawomir.ptak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16865
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>

show more ...

bdevperf: Outstanding requests array size check

Change-Id: I7bbdff40b23c3d28ae9483690d427f3c4639b651
Signed-off-by: Slawomir Ptak <slawomir.ptak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit

bdevperf: Outstanding requests array size check

Change-Id: I7bbdff40b23c3d28ae9483690d427f3c4639b651
Signed-off-by: Slawomir Ptak <slawomir.ptak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16877
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>

show more ...

bdevperf: use rand_r() twice to get 64-bit values

rand_r() only returns up to RAND_MAX which is
INT32_MAX. This means that on sufficiently large
bdevs, especially with smaller block sizes, bdevperf

bdevperf: use rand_r() twice to get 64-bit values

rand_r() only returns up to RAND_MAX which is
INT32_MAX. This means that on sufficiently large
bdevs, especially with smaller block sizes, bdevperf
may not be issuing I/O across the full range of the
bdev.

Found while investigating issue #2908.

Signed-off-by: Jim Harris <james.r.harris@intel.com>
Change-Id: I16db684a57a96f138e709008bded4471428944b6
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16768
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>

show more ...

bdevperf: Replace spdk_bdev_first/next_leaf() by spdk_for_each_bdev_leaf()

Replace all spdk_bdev_first/next_leaf() calls by spdk_for_each_bdev_leaf().

Signed-off-by: Shuhei Matsumoto <smatsumoto@nv

bdevperf: Replace spdk_bdev_first/next_leaf() by spdk_for_each_bdev_leaf()

Replace all spdk_bdev_first/next_leaf() calls by spdk_for_each_bdev_leaf().

Signed-off-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Change-Id: I61e8302346a70b0dc219fff29b06158b542dd87f
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16537
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com>

show more ...

bdevperf: Factor out creating multithread job config into helper function

The next patch will replace spdk_bdev_first/next_leaf() calls by
spdk_for_each_bdev(). As a preparation, factor out creating

bdevperf: Factor out creating multithread job config into helper function

The next patch will replace spdk_bdev_first/next_leaf() calls by
spdk_for_each_bdev(). As a preparation, factor out creating multithread
job config for a bdev into a helper function.

Signed-off-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Change-Id: Ib4df53af8b1bba5b012e93ff9d00c4089cca774e
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16536
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com>

show more ...