From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>
Cc: linux-kernel@vger.kernel.org, Waiman Long <longman@redhat.com>
Subject: [PATCH] locking/qspinlock: Fix inaccessible URL of MCS lock paper
Date: Sun, 22 Dec 2019 21:25:32 -0500 [thread overview]
Message-ID: <20191223022532.14864-1-longman@redhat.com> (raw)
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 one that is still accessible.
Signed-off-by: Waiman Long <longman@redhat.com>
---
kernel/locking/qspinlock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/locking/qspinlock.c b/kernel/locking/qspinlock.c
index 2473f10c6956..1d008d2333c0 100644
--- a/kernel/locking/qspinlock.c
+++ b/kernel/locking/qspinlock.c
@@ -34,7 +34,7 @@
* MCS lock. The paper below provides a good description for this kind
* of lock.
*
- * http://www.cise.ufl.edu/tr/DOC/REP-1992-71.pdf
+ * https://www.cs.rochester.edu/u/scott/papers/1991_TOCS_synch.pdf
*
* This queued spinlock implementation is based on the MCS lock, however to make
* it fit the 4 bytes we assume spinlock_t to be, and preserve its existing
--
2.18.1
next reply other threads:[~2019-12-23 2:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 2:25 Waiman Long [this message]
2020-01-07 12:58 ` [PATCH] locking/qspinlock: Fix inaccessible URL of MCS lock paper Peter Zijlstra
2020-01-07 13:09 ` Peter Zijlstra
2020-01-07 14:14 ` Waiman Long
2020-01-07 17:23 ` Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191223022532.14864-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox