Linux Inside

Updated 2 days ago

Jitendra Khasdev (@jitendrakhasdev) started discussion #115

4 months ago · 0 comments


These functions represents locking and unlocking based on mutex synchronization primitive. As mutex_lock will be executed, it allows us to prevent situation when two or more threads will execute this code while the mute_unlock will not be executed by process-owner of the mutex. In other words, we prevent parallel operations on a clocksource_list. Why do we need mutex here? What if two parallel processes will try to register a clock source. As we already know, the clocksource_enqueue function adds the given clock source to the clocksource_list list right after a clock source in the list which has the biggest rating (a registered clock source which has the highest frequency in the system):

Introduction to spinlocks (Edit this file)

Trivial Typo mute_unlock -> "mutex_unlock"

No description provided.

No comments on this discussion.

to join this conversation on GitBook. Already have an account? Sign in to comment

You’re not receiving notifications from this thread.

1 participant