Clarify and tweak some comments.

This commit is contained in:
John Baldwin 2004-02-27 16:14:27 +00:00
parent 03129ba97f
commit 5b7de7e19e
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=126317
2 changed files with 8 additions and 6 deletions

View File

@ -94,9 +94,9 @@ __FBSDID("$FreeBSD$");
* connected by ts_link entries is a per-thread list of all the turnstiles
* attached to locks that we own. This is used to fixup our priority when
* a lock is released. The other two lists use the ts_hash entries. The
* first of these two is turnstile chain list that a turnstile is on when
* it is attached to a lock. The second list to use ts_hash is the free
* list hung off a turnstile that is attached to a lock.
* first of these two is the turnstile chain list that a turnstile is on
* when it is attached to a lock. The second list to use ts_hash is the
* free list hung off of a turnstile that is attached to a lock.
*
* Each turnstile contains two lists of threads. The ts_blocked list is
* a linked list of threads blocked on the turnstile's lock. The

View File

@ -55,9 +55,11 @@
* on it, the new owner of the lock must claim ownership of the turnstile
* via turnstile_claim().
*
* Each thread allocates a turnstile at thread creation time via
* turnstile_alloc() and frees it at thread destroy time via
* turnstile_free().
* Each thread allocates a turnstile at thread creation via turnstile_alloc()
* and releases it at thread destruction via turnstile_free(). Note that
* a turnstile is not tied to a specific thread and that the turnstile
* released at thread destruction may not be the same turnstile that the
* thread allocated when it was created.
*
* A function can query a turnstile to see if it is empty via
* turnstile_empty(). The highest priority thread blocked on a turnstile