From 7b77abfe8893379d91bd56d7c8879aecab96a027 Mon Sep 17 00:00:00 2001 From: 0xAX Date: Sun, 10 Apr 2016 20:38:21 +0600 Subject: [PATCH] Fix a typo --- SyncPrim/sync-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SyncPrim/sync-1.md b/SyncPrim/sync-1.md index 58bcb09..c0ea09c 100644 --- a/SyncPrim/sync-1.md +++ b/SyncPrim/sync-1.md @@ -6,7 +6,7 @@ Introduction This part opens new chapter in the [linux-insides](http://0xax.gitbooks.io/linux-insides/content/) book. Timers and time management related stuff was described in The previous [chapter](https://0xax.gitbooks.io/linux-insides/content/Timers/index.html). As you may understand from the part's title, this chapter will describe [synchronization](https://en.wikipedia.org/wiki/Synchronization_%28computer_science%29) primitives in the Linux kernel. -As always, before we will consider something synchronization related, we will try to know what is `synchronization primite` in general. Actually, synchronization primitive is a software mechanism which provides ablility to two or more [concurent](https://en.wikipedia.org/wiki/Concurrent_computing) processes or threads to not execute simultaneously one the same segment of a code. For example let's look on the following piece of code: +As always, before we will consider something synchronization related, we will try to know what is `synchronization primitive` in general. Actually, synchronization primitive is a software mechanism which provides ablility to two or more [parallel](https://en.wikipedia.org/wiki/Parallel_computing) processes or threads to not execute simultaneously one the same segment of a code. For example let's look on the following piece of code: ```C mutex_lock(&clocksource_mutex);