bdevperf: add python/ dir to PYTHONPATH

The other python scripts (e.g. scripts/rpc.py) already add the relative
location of the python directory inside the repo. It's very convenient,
as it doesn't

bdevperf: add python/ dir to PYTHONPATH

The other python scripts (e.g. scripts/rpc.py) already add the relative
location of the python directory inside the repo. It's very convenient,
as it doesn't require users running them from within the repo to adjust
PYTHONPATH by themselves. Do the same for bdevperf.py.

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

show more ...

bdevperf/bdevperf.py: extend RPC timeout if needed

This patch is created to automatically extend
RPC timeout, which by default is set to 60 sec.,
if someone starts a test with longer duration.
E.g.

bdevperf/bdevperf.py: extend RPC timeout if needed

This patch is created to automatically extend
RPC timeout, which by default is set to 60 sec.,
if someone starts a test with longer duration.
E.g. the call like this:
bdevperf.py perform_tests -q 16 -o 4096 -w write -t 70
would normally result in RPC timeout during waiting for
the response, because the scheduled test will take ~70 seconds,
while the RPC timeout is 60. With this change, RPC timeout
will be set to 75 sec (5 sec longer than expected test), to
allow ample time for the test to complete.

Also, if the user explicitly specifies RPC timeout that is
shorter than the test duration, it will also be extended to
allow time for the test to complete.
I.e., for the call:
bdevperf.py -t 10 perform_tests -q 16 -o 4096 -w write -t 30
the RPC timeout will be automatically extended to 35 sec,
even though the user specified 10 sec (which is insufficient
in this case)

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

show more ...

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: promote bdevperf from test to example application

bdevperf application is utilized in multiple test scenarios
and most prominently in SPDK performance reports.
Similar to perf and fio_plug

bdevperf: promote bdevperf from test to example application

bdevperf application is utilized in multiple test scenarios
and most prominently in SPDK performance reports.
Similar to perf and fio_plugins, it is used to measure performance.
It is intended to represent the expected behavior of users
application that use SPDK bdev layer.

Applications under --enable-tests are intended for specific test
scenarios and user interaction is usually via a test scripts.
Meanwhile --enable-examples are used more broadly to teach and
show usage of SPDK libraries.

As an added benefit with this patch, its possible to compile
bdevperf without need to satisfy additional requirements to
compile all the test applications.

Change-Id: I9aaec1f9d729a1cdee89b5fdc365d61c19b03f82
Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14558
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com>
Reviewed-by: Paul Luse <paul.e.luse@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Mellanox Build Bot

show more ...