From: Matti Linnanvuori Fix a wrong path. Add a chapter about try functions. http://bugzilla.kernel.org/show_bug.cgi?id=9011 Signed-off-by: Matti Linnanvuori Signed-off-by: Randy Dunlap Cc: Rusty Russell Signed-off-by: Andrew Morton --- Documentation/DocBook/kernel-locking.tmpl | 25 +++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff -puN Documentation/DocBook/kernel-locking.tmpl~docbook-some-kernel-locking-fixes Documentation/DocBook/kernel-locking.tmpl --- a/Documentation/DocBook/kernel-locking.tmpl~docbook-some-kernel-locking-fixes +++ a/Documentation/DocBook/kernel-locking.tmpl @@ -290,7 +290,7 @@ If you have a data structure which is only ever accessed from user context, then you can use a simple semaphore - (linux/asm/semaphore.h) to protect it. This + (include/asm/semaphore.h) to protect it. This is the most trivial case: you initialize the semaphore to the number of resources available (usually 1), and call down_interruptible() to grab the semaphore, and @@ -703,6 +703,29 @@ + + The try variants + + + spin_trylock() does not spin but returns non-zero if + it acquires the spinlock on the first try or 0 if not. + + + + mutex_trylock() does not suspend your task + but returns non-zero if it could lock the mutex on the first try + or 0 if not. + + + + down_trylock() does not suspend your task + but returns 0 if it could get the semaphore on the first try or + non-zero if not. The return value is the inverse of that of + spin_trylock() and mutex_trylock() + . + + + Common Examples _