Thanks for your efforts. Surely you will have millions of students/subscribers in 2019. Pray for the best for you. Your videos are enrich with matter and very informative.
Modern multithreading API's can do context switching between the threads so that even if one of the child thread is blocked the other threads will keep running. (Good lecture)
Even older multithreaded system can do context switching between thread but there will no kernel level thread available to map that user level thread because m:1 mapping. But modern multithreaded api mostly working with m:n so blocking of one thread doesn't affect other
i watched ur one video and loved it.....and i continued watching related my topics.......all ur info.....is very helpful as my exams are their tomorrow....ty sir
this topic is complex but after watching this video you will be able to solve the questions easily. Fork questions are asked in competitive exams like GATE, NTA NET, NIELIT, DSSSB tgt/ pgt computer science, KVS CSE, PSUs etc and college university exams also.
But then what is the difference b/w process and kernel level threads? Is it simply the fact that the memory is not cloned in case of kernel level threads? So does kernel level threads only differ from user-level threads in the fact that the former is acknowledged to be different subroutine?
In previous lecture (Process vs Thread), if one thread is get blocked then whole process is get blocked i e which blocked all threads of that process, In this lecture, kernal level threads are non blocking, blocking of one thread not blocking executions of other thread Thank you
Thanku sir for such a nice resource not only in os your dbms playlist is also superb today I got placed in VMware n I followed your videos n it helped me a lot mere jaise aur v kitne honge thanku for such resources ❤️❤️❤️❤️
Sir i have a question can u tell me, If kernel level thread share code and data then in case of blocking why it is independent doesn't effect others like a process. And ek or baat sir, u r exceptionali talented.
since os is aware of kernel threads hence blocking one thread won't affect other whereas in user level os treats thread as a single process. So blocking a thread means blocking a complete process in user level.
Divya Mehta i like your curiousity but i didn't get it till now because both thread (kernel/user level) share code and data then OS should block both type of threads in case of blocking becoz they have common code & data. I hope u got my point!! That's why i asked it to sir.
@@kanhaiyasharma6421 bcz user level thread is hidden from OS so Os Handle it as single process and other side Os is aware of kernal level thread so handle it partially 😅
Kanhaiya Sharma in the kernel level the process id’s are different so the os treats it as two different process and blocking one kernel thread doesnt effect the other while in user level thread the process id is same so blocking one thread will also the other threads Hope I cleared your doubt Thanks!
One question.....Sir, I liked understood this concept by you.. And the question is how we could understand that the process is running or thread is running ? And can I get any examples of KLT and UerLevel Thread in the os environment.?
Hi Sir, awesome explanation...but I have some doubts.. KLT doesn't block other threads as Process doesn't block other processes....But KLT share the same data and code within the Process just like ULT does because its a thread....seems KLT has some properties matching to ULT and some to Process(like kernel involvement)...now here the question is, how kernel is aware of KLT if it also uses the same Process ID, same code and data from process....surely kernel is aware of, thats why its not blocking other KLTs for any I/O requests.
Agar aapke jese teacher ho university me to koy bhi bunk na kare ek bhi lecture amzing sir kal mera exam hai or me sirf aapke video dekh k hi jata hu and i know ki aapne jo karaya unme se thoda bhi likhunga to pass to ho hi jaunga🙏
At 5:30, why do we say that when a user level thread performs blocking then the kernel blocks all processes? Aren't user level threads independent of the control of the kernel?
Sir 07:47 you said in GATE question was asked that kernel level thread do not share the code. Later at 07:57 you are saying both user level and kernel level thread share the code and data. Which one is correct???
Indian private engineering colleges need teacher like you sir.
Why only private? Even IITs need him :)
@@abhishekpawar2127 r u from IIT?
@@mohammedumarfarhan9900 yeah.
No buddy, Not only private colleges,Also need government colleges ..^_^
💯
Such complex concepts explained in such a simple way. Thank you !
Hii love you 😘
@@shivmahto69 and I love you 😘
@@bhaveshkumar6842 And I love you
@@vineetsingh3374 thanks bhai. Aise hi apna pyaar bana rahe
Kitna parivarik mahol hai 😂 love you guys ❤️
The way You teach, I don't think you need to ask for any like subscribe & share at the end of every video .. :) excellent teaching sir
I am also a University Professor but love to see your teaching style, easily understandable. Stay blessed, Love from Pakistan!
exactly, love and respect from Pakistan
Pakistan will be a part of India Soon
You know shehar me dehat
Love from India ❤
Kiss uni MN hn app Sir
Thanks for your efforts. Surely you will have millions of students/subscribers in 2019. Pray for the best for you. Your videos are enrich with matter and very informative.
Neither bulky paragraph... nor unusual extra knowledge..just to the point and simple explanation ♥️
Modern multithreading API's can do context switching between the threads so that even if one of the child thread is blocked the other threads will keep running. (Good lecture)
Even older multithreaded system can do context switching between thread but there will no kernel level thread available to map that user level thread because m:1 mapping. But modern multithreaded api mostly working with m:n so blocking of one thread doesn't affect other
i watched ur one video and loved it.....and i continued watching related my topics.......all ur info.....is very helpful as my exams are their tomorrow....ty sir
if you provide notes for semester exam it will be more useful. thank u for great learning😊
soon going to have 1 lakh subscribers..one of the fastest growing educational channel.
You make each and every concept crystal clear. Your teaching style is the best!!
The entire video was in Indian yet I understood more than I did with my professor, thanks man!
Thank you so much for your hard work! The concepts are thoroughly explained😊
Sir ur Way of teaching is fantastic I thought this subject was so boring but u made it interesting
Thank you so much sir for explaining the explains the contents of threads, You way of teaching is excellent ❤
Sir AP bht achha samjhte h aise he video banate rhyye os mai😍
thnkkk u so much sir ji......vry great expalnation....endless teaching....stay blessed..
this topic is complex but after watching this video you will be able to solve the questions easily. Fork questions are asked in competitive exams like GATE, NTA NET, NIELIT, DSSSB tgt/ pgt computer science, KVS CSE, PSUs etc and college university exams also.
Perfect explanation ....all videos are great than my college teacher 👍
Thanks sir for regularly uploading
But then what is the difference b/w process and kernel level threads? Is it simply the fact that the memory is not cloned in case of kernel level threads? So does kernel level threads only differ from user-level threads in the fact that the former is acknowledged to be different subroutine?
You are best teacher...thank you so much sir.....
Great explanation as always! ❤
Outstanding explanation sir ❤🔥
157 LIKES. 0 DISLIKES. GREAT WORK SIR
Itna acha smjhaty sir aap big fan of you🥺💞
best and easy way to learn and understand fast .....thanks so much sir
Very helpful teaching 😍
Tank you sir
Sir ji…Tussi Great Ho 🔥🔥
Your classes are very interesting ❤️👍
sir, my all doubts got cleared on your os playlist. thanks sir
bro...tumhara bhi exam hai kya os ka aaj...hahaha
first time watch your video sir its v help full............ thanks sir
In previous lecture (Process vs Thread), if one thread is get blocked then whole process is get blocked i e which blocked all threads of that process,
In this lecture, kernal level threads are non blocking, blocking of one thread not blocking executions of other thread
Thank you
Sir, you explained the lecture very well . thanks
I'm watching from Pakistan You're a good Teacher thanks for whole playlist ❤️
you are explaining very nicely and i understand properly.thank you for making such a nice videos
Great work sir!! Keep it up❤❤
Sir ur really great teacher
God bless u Sir...Really like ur way of teaching
All videos are explanation of the book "A Handbook on Computer Science & IT".
Awesome explanation.
Jabardast video.
Keep it up.
Thanx a lot.
Gud explanation....thanks sir..🙏
what a teacher dude you are fab
Lecture successfully completed on 05/12/2024 🔥🔥
very awesome video sir.
I really liking all the videos of you sir. Really I am telling from bottom of my heart ❤️💛
Great sir all doubts are clear...
❤❤❤
Thnk u Sir.Your explanation is Op
Next level explanation .
gurujee tussi great ho
Excellent explanation👏
Thanku sir for such a nice resource not only in os your dbms playlist is also superb today I got placed in VMware n I followed your videos n it helped me a lot mere jaise aur v kitne honge thanku for such resources ❤️❤️❤️❤️
Congratulations..you can share your details at gatesmashers2018@gmail.com
Keep going sir ji best de rhe ho aap apna videos banana stop mt krna
God bless u sir
Sir i have a question can u tell me,
If kernel level thread share code and data then in case of blocking why it is independent doesn't effect others like a process.
And ek or baat sir, u r exceptionali talented.
since os is aware of kernel threads hence blocking one thread won't affect other whereas in user level os treats thread as a single process. So blocking a thread means blocking a complete process in user level.
Divya Mehta i like your curiousity but i didn't get it till now because both thread (kernel/user level) share code and data then OS should block both type of threads in case of blocking becoz they have common code & data.
I hope u got my point!!
That's why i asked it to sir.
@@kanhaiyasharma6421 bcz user level thread is hidden from OS so Os Handle it as single process and other side Os is aware of kernal level thread so handle it partially 😅
Kanhaiya Sharma in the kernel level the process id’s are different so the os treats it as two different process and blocking one kernel thread doesnt effect the other while in user level thread the process id is same so blocking one thread will also the other threads
Hope I cleared your doubt
Thanks!
Shirt kmal ki h 😎
Lecture tu or b amazing h
One question.....Sir,
I liked understood this concept by you..
And the question is how we could understand that the process is running or thread is running ?
And can I get any examples of KLT and UerLevel Thread in the os environment.?
thank u vai..love from nepal
Excellent.
Thank you sir.. I have already started recommending your channel because you are the best teacher for computer science on youTube. 🙂
Hi Sir, awesome explanation...but I have some doubts..
KLT doesn't block other threads as Process doesn't block other processes....But KLT share the same data and code within the Process just like ULT does because its a thread....seems KLT has some properties matching to ULT and some to Process(like kernel involvement)...now here the question is, how kernel is aware of KLT if it also uses the same Process ID, same code and data from process....surely kernel is aware of, thats why its not blocking other KLTs for any I/O requests.
Tum jio hazaro saal or bnao lakho videos hmare liye taki college wale hamara kuchh na bigad sake sir ji tussi great Ho 🤗🤗🤗🤗😃😃
Tank you sir....
Simple and awesome explanation
Love you so much Varun bhai! Amazing
Sir mind blowing explanation......keep doing it helps so many students
Sir, Though I am not in your class. Seeing your videos is like learning in classroom. Really nice!
Thanku so much sir
Agar aapke jese teacher ho university me to koy bhi bunk na kare ek bhi lecture amzing sir kal mera exam hai or me sirf aapke video dekh k hi jata hu and i know ki aapne jo karaya unme se thoda bhi likhunga to pass to ho hi jaunga🙏
Lol
Thank you Mr so much
your the best one I like your way of teaching
Good ...
Thank you sir 🙏❤
At 5:30, why do we say that when a user level thread performs blocking then the kernel blocks all processes? Aren't user level threads independent of the control of the kernel?
nice explain sir.....pls attach questions and answers of particular topic in description box🙏❤️
Thanks sir....
Great stuff! Should make the videos in english it will attract a bigger crowd :) Not many good english OS videos taught as well as yours
Thanks sir
Thank you so much
Good content sir..keep it up
Thank you so much sir
Sir can u please tell us about the context switching time between two process and between user mode and kernel mode .which takes more time
Sir 07:47 you said in GATE question was asked that kernel level thread do not share the code. Later at 07:57 you are saying both user level and kernel level thread share the code and data. Which one is correct???
My exam tomorrow its very useful now thanks sir
All the Best
Wooooowwwwwww!!!!!!!!
congrates for 1M subscribers
Assalamualaikum
Huge respect from pakistan🙂
v nice
👌👌👌👌👌👌
amazing
धन्यवाद सर
Thanks you sir❤❤ helped me last moment of exam
I am from Pakistan
🔥
4:44 blocking operation. Marking for future ref.
Nice
Good job brother
thank you you are the besttttt
thx
Thanks sir g
Ab koe issue nae hota os sub mn thankuu sir
Sir please provide different sets of question in the currnet topic for kernal level thread .It would be a great help........
you are very good teacher.your explanation is too good.apka name keya hain??