38527b0786
Before enabling SPDK thread scheduler, each POSIX thread name was reactor_% (% was the core number). After enabling SPDK thread scheduler, the name of the master POSIX thread is reactor_% (% is the max core number), and the name of the slave posix threads are lcore-slave-% (% is the current core number). SPDK threads are light-weight threads - sometimes also called green threads or fibers, and so are independent from posix threads. But reactor is tied to the POSIX thread in the SPDK event library. So SPDK thread doesn't rename the POSIX thread at its creation but reactor renames the POSIX thread at start instead. This change makes POSIX thread name compatible between before and after enabling SPDK thread scheduler. Change-Id: I26e8dabc73e163c9f74e18b3640cf54954603b1f Signed-off-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/451712 Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
---|---|---|
.. | ||
bdev | ||
blob | ||
blobfs | ||
conf | ||
copy | ||
env_dpdk | ||
event | ||
ftl | ||
ioat | ||
iscsi | ||
json | ||
jsonrpc | ||
log | ||
lvol | ||
nbd | ||
net | ||
notify | ||
nvme | ||
nvmf | ||
reduce | ||
rocksdb | ||
rpc | ||
scsi | ||
sock | ||
thread | ||
trace | ||
ut_mock | ||
util | ||
vhost | ||
virtio | ||
Makefile |