summaryrefslogtreecommitdiffstats
path: root/include/asm-ia64/semaphore.h
diff options
context:
space:
mode:
Diffstat (limited to 'include/asm-ia64/semaphore.h')
-rw-r--r--include/asm-ia64/semaphore.h7
1 files changed, 0 insertions, 7 deletions
diff --git a/include/asm-ia64/semaphore.h b/include/asm-ia64/semaphore.h
index 2c75056c5..a50ee01e3 100644
--- a/include/asm-ia64/semaphore.h
+++ b/include/asm-ia64/semaphore.h
@@ -137,13 +137,6 @@ up (struct semaphore * sem)
* In terms of fairness, when there is heavy use of the lock, we want
* to see the lock being passed back and forth between readers and
* writers (like in a producer/consumer style of communication).
- *
-
- For
- * liveness, it would be necessary to process the blocked readers and
- * writers in FIFO order. However, we don't do this (yet). I suppose
- * if you have a lock that is _that_ heavily contested, you're in big
- * trouble anyhow.
*
* -ben (with clarifications & IA-64 comments by davidm)
*/