CPU Scheduling Basics

[@yanistancheva3076]

16 minutes summed up my whole 2 hour lecture thank you

[@JacobSorber]

You're welcome. Glad I could help.

[@ukaszkiepas57]

+1

[@user-ej7ss8ei2g]

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.

[@abanoubsameh6608]

Great videos! I wish I found you earlier. Keep up the good work.

[@Christobanistan]

I've been a programming since 1989 or so, always wondered about this but never got around to this. Cool beans.

[@santoshsco]

Love your channel jacob , wish i had found this earlier .

[@JacobSorber]

Thanks, Santosh. Glad you're enjoying it.

[@g194g]

Very clear and helpful explanation

[@jonathanflores3748]

Great content! Love your videos!

[@JacobSorber]

Thanks, Jonathan. Glad you like them!

[@smallspringonion]

Very helpful video! Thank you!

[@JacobSorber]

You're welcome.

[@XxxGuitarMadnessxxX]

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

[@JacobSorber]

Glad you enjoyed that.

[@roargamer007]

2:02 Process States Created = New Active = Running Waiting Ready Exited = Terminated

[@randomsoul00]

well explained👍

[@omhmpp]

absolutely phenomenal video, but I just wanna point out that SJF (shortest job first) is actually different than shortest remaining time first SRTF

[@jenselstner5527]

Best of video is the LEGO in the background ... just kidding. ;o) Good explanation and nice LEGOs.

[@marziehizadi985]

Fantastic, thanks a lot.

[@bigwoof2137]

Avg. Response time 7:51 is wrong, should be 4.33. P1: 0 P2: 7 - 2 = 5 P3: 7 + 4 - 3 = 8

[@donha475]

Lol @ -20 niceness impersonation ;)

[@pasteyourinjectionstringhere]

HAHAHA

[@bad_robot]

the scout law reference lol

[@kushagrakumar9576]

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 .

[@JacobSorber]

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.

[@kushagrakumar9576]

@@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 .?

[@oviya.n1317]

Pls make playlists for OS and embedded system

[@ropersonline]

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...?

[@JacobSorber]

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.

[@ropersonline]

@@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. :)

[@maoryatskan6346]

Awesome

[@MB-hs4vp]

Do these scheduling techniques differ for RTOS?

[@JacobSorber]

Yes. In real-time scheduling tasks have deadlines, and the scheduler has to reason about those deadlines.

[@ailijic]

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.

[@ropersonline]

@@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.

[@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.

[@aubriewest1135]

14:59 Sounds like Ta'arof in Iran :)

[@BritishBeachcomber]

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.

[@Axias85]

....Wait, was that a Boy Scout joke?

[@joerogan3079]

*MY PROF IS HORRIBLE* 🤦‍♂️ #helpMe

[@alacastersoi8265]

"7,214 views" ? wHaT?

[@faizunisajazadi8732]

Great lecture! Thanks!