Skip to content

Commit 5709712

Browse files
Waiman-LongPeter Zijlstra
authored andcommitted
locking/qspinlock: Fix inaccessible URL of MCS lock paper
It turns out that the URL of the MCS lock paper listed in the source code is no longer accessible. I did got question about where the paper was. This patch updates the URL to BZ 206115 which contains a copy of the paper from https://www.cs.rochester.edu/u/scott/papers/1991_TOCS_synch.pdf Signed-off-by: Waiman Long <[email protected]> Signed-off-by: Peter Zijlstra (Intel) <[email protected]> Acked-by: Will Deacon <[email protected]> Link: https://lkml.kernel.org/r/[email protected]
1 parent a030f97 commit 5709712

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

kernel/locking/qspinlock.c

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -31,14 +31,15 @@
3131
/*
3232
* The basic principle of a queue-based spinlock can best be understood
3333
* by studying a classic queue-based spinlock implementation called the
34-
* MCS lock. The paper below provides a good description for this kind
35-
* of lock.
34+
* MCS lock. A copy of the original MCS lock paper ("Algorithms for Scalable
35+
* Synchronization on Shared-Memory Multiprocessors by Mellor-Crummey and
36+
* Scott") is available at
3637
*
37-
* http://www.cise.ufl.edu/tr/DOC/REP-1992-71.pdf
38+
* https://bugzilla.kernel.org/show_bug.cgi?id=206115
3839
*
39-
* This queued spinlock implementation is based on the MCS lock, however to make
40-
* it fit the 4 bytes we assume spinlock_t to be, and preserve its existing
41-
* API, we must modify it somehow.
40+
* This queued spinlock implementation is based on the MCS lock, however to
41+
* make it fit the 4 bytes we assume spinlock_t to be, and preserve its
42+
* existing API, we must modify it somehow.
4243
*
4344
* In particular; where the traditional MCS lock consists of a tail pointer
4445
* (8 bytes) and needs the next pointer (another 8 bytes) of its own node to

0 commit comments

Comments
 (0)