stundent starvation for os ends here , indeed such aa gemmm 🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌
@LavanayaMalhotra-k1m4 ай бұрын
00:07 Disadvantage: Busy Waiting in Semaphores 01:31 Busy waiting in semaphores wastes CPU cycles 02:46 Modifying weight and signal operations to overcome busy waiting 04:06 Blocking a process prevents it from busy waiting 05:27 Implementing semaphores with waiting queue can lead to deadlocks and starvation. 06:50 Deadlock can occur when using semaphores. 08:13 Concurrency issues with semaphore usage 09:40 Semaphores can lead to deadlocks Crafted by Merlin AI.
@nightcrawler4293 Жыл бұрын
1- Semaphores belongs to the non-active waiting solutions for synchronization . passive waiting solutions : semaphores , locks , cs , monitor . 2 - the solution you discussed , we took it in college as the semaphore form directly .
@findynx10 ай бұрын
l enjoyed the tutorial, so insightful and well presented. Thank you!!
@kwakuboateng75252 жыл бұрын
Wowww. Lovely teachings. Do you have a website where I can learn more?. Very well done!! :)
@VivekRaj-kk5jb3 жыл бұрын
Please unlock rest of the chapters like deadlock, virtual memory etc. so that we can complete the course.
@nesoacademy3 жыл бұрын
Hi, you can access them on our website/app after getting the Neso Fuel.
@PradeepYadav-fg2yg3 жыл бұрын
@@nesoacademy what is neso fuel
@josephjoy70803 жыл бұрын
@@PradeepYadav-fg2yg its a subscription$ , i would subscribe if i was you. his OS videos are the best and the prices are really cheap compared to other!
@nikunjhemani7093 Жыл бұрын
@@josephjoy7080 neso ka broker😂😂😂
@sharondjongo9470 Жыл бұрын
Merci beaucoup.
@c.d.premkumar68672 жыл бұрын
It is not "need for busy wIting" it should be "overcome the problem of busy waiting".
@rahulshaw74573 жыл бұрын
Nice sir❣️❣️❣️❣️
@keremaksoy80073 жыл бұрын
I think the deadlock is not about only the semaphores with waiting quaes. It can also happens with binary semaphores if we implement them in a same way like in the video, am I right ?
@kerematasen3993 жыл бұрын
I guess so.
@adolfocarrillo2482 жыл бұрын
No, deadlock can not happen in a binary semaphore, a binary semaphore is like a mutual exclusion algorithm.
@NisargaChowdaiah10 ай бұрын
No, bcz binary semaphores only for 2 processes
@AbhishekKumar-kk6qs Жыл бұрын
This busy waiting for all solution you discussed all have this busy waiting.
@MeabuOP Жыл бұрын
thats what i think
@unmandarinoalgiorno...93217 ай бұрын
@@MeabuOP Indeed i didn't understand the waiting-queue solution to resolve busy waiting problem. It seems to me that the busy waiting exists always.
@samibouguerra3154Ай бұрын
@@unmandarinoalgiorno...9321 when its on busy waiting it drains the cpu and that happens when its on the while loop , now when it blocks itself by entering a waiting queue its not on the while loop so it doesnt drain cpu thats what he explained
@venkataswamykadiyam9773 жыл бұрын
Please upload atleast 2 videos for a day sir
@mdminhazulislamroyel270910 ай бұрын
End on ONE NIGHT RUN
@Sparkler210 Жыл бұрын
Deadlock: Resource1 Assigned to Waiting for Process1 Process2 Waiting for assigned to Resource2
@clv6032 ай бұрын
CPU scheduler: I'm just doing my job
@narimanvatankhah12696 ай бұрын
@mudassarsiddiqui41122 жыл бұрын
👍👍
@udbhavvikramsingh34493 жыл бұрын
I didn't understand what is two semaphore S & Q means here Why process need two semaphore 🤔🤔🤔🤔
@shaziasamreen85843 жыл бұрын
Each resources has its own semaphore. So think it as P0 is first trying for resource S and P1 is trying for Resource Q.After they get them P0 will wait for Resource Q which is acquired by P1 and P1 will wait for resource S which is acquired by P0 which is a deadlock condition.Hope this helps.Correct me of I am wrong