summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorNilay Shroff <nilay@linux.ibm.com>2024-11-05 11:42:08 +0530
committerKeith Busch <kbusch@kernel.org>2024-11-19 07:49:48 -0800
commit84488282166de6b6760ada8030e87aaa08bce3aa (patch)
tree610020509c3abb834149839a7ceb201254bcda7b /tools/perf/scripts/python/exported-sql-viewer.py
parent6fad84a4d624c300d03ebba457cc641765050c43 (diff)
downloadlinux-stable-84488282166de6b6760ada8030e87aaa08bce3aa.tar.gz
linux-stable-84488282166de6b6760ada8030e87aaa08bce3aa.tar.bz2
linux-stable-84488282166de6b6760ada8030e87aaa08bce3aa.zip
Revert "nvme: make keep-alive synchronous operation"
This reverts commit d06923670b5a5f609603d4a9fee4dec02d38de9c. It was realized that the fix implemented to contain the race condition among the keep alive task and the fabric shutdown code path in the commit d06923670b5ia ("nvme: make keep-alive synchronous operation") is not optimal. The reason being keep-alive runs under the workqueue and making it synchronous would waste a workqueue context. Furthermore, we later found that the above race condition is a regression caused due to the changes implemented in commit a54a93d0e359 ("nvme: move stopping keep-alive into nvme_uninit_ctrl()"). So we decided to revert the commit d06923670b5a ("nvme: make keep-alive synchronous operation") and then fix the regression. Link: https://lore.kernel.org/all/196f4013-3bbf-43ff-98b4-9cb2a96c20c2@grimberg.me/ Reviewed-by: Ming Lei <ming.lei@redhat.com> Signed-off-by: Nilay Shroff <nilay@linux.ibm.com> Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions