Jim Harris 120a6c1c2a nvmf: do not encode core number into thread name ... The nvmf subsystem cannot control which core its threads get scheduled on. Even in the normal, default case, the app thread has already been scheduled on the first core, so the first nvmf thread will get scheduled on the second core, etc. So instead, always use a 0-based index for the names of the nvmf threads. Reported-by: Jacek Kalwas <jacek.kalwas@intel.com> Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I8a0f161860b985f36920845de28b39dbae9fdca5 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/11351 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jacek Kalwas <jacek.kalwas@intel.com>		2022-01-31 09:43:16 +00:00
..
subsystems	nvmf: do not encode core number into thread name	2022-01-31 09:43:16 +00:00
Makefile	event: move app_rpc contents	2020-09-25 11:43:42 +00:00