[SERVER-36628] SpinLock should remember what thread is holding it Created: 13/Aug/18  Updated: 16/Aug/18  Resolved: 16/Aug/18

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-36629 Hang analyzer should print what threa... Closed
Related
is related to SERVER-36676 Back SpinLock with a stdx::mutex in d... Closed
Participants:

 Comments   
Comment by Mira Carey [ 16/Aug/18 ]

I think we're resistant to adding extra overhead to spinlock in non-debug builds.

For debug builds SERVER-36676 offers deadlock detection on linux (and for windows builds the critical section it holds already has debuggability)

Generated at Thu Feb 08 04:43:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.