16 minutes summed up my whole 2 hour lecture thank you
@JacobSorber3 жыл бұрын
You're welcome. Glad I could help.
@ukaszkiepas572 жыл бұрын
+1
@user-ej7ss8ei2g3 жыл бұрын
Hah, imagine having a teacher or prof. so cool that they have their own high quality channel, but also says when something might show up on a quiz. Love the videos, you've helped me a lot.
@Christobanistan2 жыл бұрын
I've been a programming since 1989 or so, always wondered about this but never got around to this. Cool beans.
@abanoubsameh66083 жыл бұрын
Great videos! I wish I found you earlier. Keep up the good work.
@roargamer007Ай бұрын
2:02 Process States Created = New Active = Running Waiting Ready Exited = Terminated
@santoshsco3 жыл бұрын
Love your channel jacob , wish i had found this earlier .
@JacobSorber3 жыл бұрын
Thanks, Santosh. Glad you're enjoying it.
@g194g4 жыл бұрын
Very clear and helpful explanation
@omhmpp2 жыл бұрын
absolutely phenomenal video, but I just wanna point out that SJF (shortest job first) is actually different than shortest remaining time first SRTF
@totalyunsober4 жыл бұрын
Very helpful video! Thank you!
@JacobSorber4 жыл бұрын
You're welcome.
@jonathanflores37484 жыл бұрын
Great content! Love your videos!
@JacobSorber4 жыл бұрын
Thanks, Jonathan. Glad you like them!
@bigwoof21376 ай бұрын
Avg. Response time 7:51 is wrong, should be 4.33. P1: 0 P2: 7 - 2 = 5 P3: 7 + 4 - 3 = 8
@bad_robot6 ай бұрын
the scout law reference lol
@kushagrakumar95765 жыл бұрын
What is the difference between chrt and nice utility for process scheduling in linux? Could you please explain sched_setscheduler ( sched.h ) and related system call with an example .
@JacobSorber5 жыл бұрын
chrt is more general and more powerful than nice. Nice basically changes the inverse of the processes priority assuming the default Linux scheduler. With chrt, you can change the scheduler. Linux offers a few different schedulers (check the chrt man page for details), and the naming is a bit misleading, because they refer to "real-time" scheduling, but Linux isn't a RTOS. So, this isn't real real-time scheduling (no deadlines). It's just a higher priority scheduling algorithm. If you need an RTOS (you're implementing flight control on an airplane or running a self-driving car) I would recommend looking somewhere other than Linux.
@kushagrakumar95765 жыл бұрын
@@JacobSorber Thanks Jacob for the explanation. Please continue to make more videos on OS. Do you think is it worth to make a continuation video on process scheduling with More system calls like sched_setscheduler etc .?
@donha4754 жыл бұрын
Lol @ -20 niceness impersonation ;)
@pasteyourinjectionstringhere2 ай бұрын
HAHAHA
@corcodelmarian Жыл бұрын
On Intel proc allways look to call and jump to be paired with ret on binary Code but, gcc forget sometimes, this îs big problem on linux.
@XxxGuitarMadnessxxX3 жыл бұрын
I've been watching your videos for a little while now (Great Content by the way! Loving the neat tricks you can learn from watching your videos!) But I died when you started quoting the whole B.S. oath - It's been 10 years since I heard all that lmao
@JacobSorber3 жыл бұрын
Glad you enjoyed that.
@marziehizadi9852 жыл бұрын
Fantastic, thanks a lot.
@oviya.n13173 жыл бұрын
Pls make playlists for OS and embedded system
@randomsoul002 жыл бұрын
well explained👍
@maoryatskan63464 жыл бұрын
Awesome
@jenselstner55273 жыл бұрын
Best of video is the LEGO in the background ... just kidding. ;o) Good explanation and nice LEGOs.
@MB-hs4vp6 жыл бұрын
Do these scheduling techniques differ for RTOS?
@JacobSorber6 жыл бұрын
Yes. In real-time scheduling tasks have deadlines, and the scheduler has to reason about those deadlines.
@ailijic5 жыл бұрын
Some RTOS can have both real time and standard tasks. Also, the Linux kernel can have real time tasks. Real time is a very overused term. Know the requirements of your system and then look for an OS that can handle those requirements.
@ropersonline4 жыл бұрын
@@ailijic It's not just the OS; go look for suitable silicon also. Back in the day that might have been Motorola 68k or even MOS 6502. These days it's prolly s/th like ARM Cortex-R.
@ropersonline4 жыл бұрын
11:50: "If alpha is one, then we ignore reality and we just go with the last prediction... If alpha is close to zero, we predict almost solely based on the last experience..." So either the last or the last? That doesn't seem to make too much sense...?
@JacobSorber4 жыл бұрын
There's the last prediction (p_n, what we predicted last) and the last experience (m, what actually happened last). They're both "last" things, but different things. Sorry for the confusion.
@ropersonline4 жыл бұрын
@@JacobSorber Thanks for taking the time and answering everything. You're really nice, and not in the scheduling sense either. :) I plan to watch all your videos, but there's a whole year's worth still left. :)
@BritishBeachcomber2 жыл бұрын
The OS/2 scheduler was so bad. If a task/thread went into an infinite loop, with no system calls, the whole system would hang.