Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 9ba0bdfd authored by Jan Altenberg's avatar Jan Altenberg Committed by Linus Torvalds
Browse files

[PATCH] typo fixes for rt-mutex-design.txt 



Address some simple typos in rt-mutex-design.txt It also changes the
indentation of the cmpxchg example (the cmpxchg example was indented by
spaces, while all other code snippets were indented by tabs).

Acked-by: default avatarSteven Rostedt <rostedt@goodmis.org>
Signed-off-by: default avatarJan Altenberg <tb10alj@tglx.de>
Acked-by: default avatarIngo Molnar <mingo@elte.hu>
Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
parent 710b8b5f

Documentation/rt-mutex-design.txt

+7 −7
Original line number Original line Diff line number Diff line
@@ -582,7 +582,7 @@ contention). 
try_to_take_rt_mutex is used every time the task tries to grab a mutex in the

try_to_take_rt_mutex is used every time the task tries to grab a mutex in the

slow path.  The first thing that is done here is an atomic setting of

slow path.  The first thing that is done here is an atomic setting of

the "Has Waiters" flag of the mutex's owner field.  Yes, this could really

the "Has Waiters" flag of the mutex's owner field.  Yes, this could really

be false, because if the the mutex has no owner, there are no waiters and

be false, because if the mutex has no owner, there are no waiters and

the current task also won't have any waiters.  But we don't have the lock

the current task also won't have any waiters.  But we don't have the lock

yet, so we assume we are going to be a waiter.  The reason for this is to

yet, so we assume we are going to be a waiter.  The reason for this is to

play nice for those architectures that do have CMPXCHG.  By setting this flag

play nice for those architectures that do have CMPXCHG.  By setting this flag
@@ -735,7 +735,7 @@ do have CMPXCHG, that check is done in the fast path, but it is still needed 
in the slow path too.  If a waiter of a mutex woke up because of a signal

in the slow path too.  If a waiter of a mutex woke up because of a signal

or timeout between the time the owner failed the fast path CMPXCHG check and

or timeout between the time the owner failed the fast path CMPXCHG check and

the grabbing of the wait_lock, the mutex may not have any waiters, thus the

the grabbing of the wait_lock, the mutex may not have any waiters, thus the

owner still needs to make this check. If there are no waiters than the mutex

owner still needs to make this check. If there are no waiters then the mutex

owner field is set to NULL, the wait_lock is released and nothing more is

owner field is set to NULL, the wait_lock is released and nothing more is

needed.

needed.