Groups | Search | Server Info | Keyboard shortcuts | Login | Register
Groups > comp.os.linux.development.system > #785
| Newsgroups | comp.os.linux.development.system |
|---|---|
| Date | 2019-01-08 09:36 -0800 |
| Message-ID | <b11d3140-d4fc-4831-a6f9-2f94ddc1fe99@googlegroups.com> (permalink) |
| Subject | Spinlocks and Semaphores |
| From | sarthak.kelapure@gmail.com |
I have few queries, I think you can help me with them. Please do try. 1. The Linux kernel enforces the following policy: a process is not allowed to try to acquire a semaphore while it is already holding a spin lock. Why is it so and what will happen if we break this rule? 2. What are the problems that occurs when using spinlocks on a single processor system(preemptible kernel and a non-preemptible kernel) 3. What concurrency issues can arise when the up() (increment counter) and down() (decrement counter) functions of a semaphore are not executed atomically. How is it important?
Back to comp.os.linux.development.system | Previous | Next | Find similar
Spinlocks and Semaphores sarthak.kelapure@gmail.com - 2019-01-08 09:36 -0800
csiph-web