6052d9a432
A short delay is required between starting up a primary and secondary process with DPDK depending on what the secondary depends on wrt the primary. As the SPDK sample apps are not designed to be dependent on each other, when we use them as primary/secondary in test scripts with no deterministic synchronization, it is possible for one ore more to hang resulting in DPDK fatal init failures. Often times this would show up as a failure to get hugepages in vtophys A related fix, same failing signature in the same test script, is also included here where the stub app, which is designed to act as primary in certain sections of the test script, was being killed by the test script but the next primary app was coming up before the process was dead and coming up as a secondary. A wait was added to assure that the stub process is gone before the next app tries to start. Change-Id: If2f6fc25e76b769ad8edafa8e965be246e98dab9 Signed-off-by: Paul Luse <paul.e.luse@intel.com> Reviewed-on: https://review.gerrithub.io/367725 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> |
||
|---|---|---|
| .. | ||
| perf/nvme | ||
| vagrant | ||
| autotest_common.sh | ||
| build_kmod.sh | ||
| check_format.sh | ||
| detect_cc.sh | ||
| eofnl | ||
| fio.py | ||
| gen_nvme.sh | ||
| genconfig.py | ||
| posix.txt | ||
| prep_benchmarks.sh | ||
| rpc.py | ||
| setup.sh | ||