Gregory's Serverwaiwaitwait ok I don't know anything about this and I just skimmed some webpage but correct me if I'm wrong
- the kernel keeps track of processes/threads
- running programs need to do syscalls to allocate memory and do other things
- when the syscalls happen it's the kernel's time to do things and it can decide whether to return to the calling process or to run other processes
is that how it works :akko_derp:
(got that idea from this paragraph)
> The other place you might want to update the amount of time a task has consumed is immediately after the CPU changes from user-space code to kernel code and immediately before the CPU changes from kernel code to user-space code
https://wiki.osdev.org/Brendan's_Multi-tasking_Tutorial
there's a lot of buzzwords that I need to look up
this is interesting
- the kernel keeps track of processes/threads
- running programs need to do syscalls to allocate memory and do other things
- when the syscalls happen it's the kernel's time to do things and it can decide whether to return to the calling process or to run other processes
is that how it works :akko_derp:
(got that idea from this paragraph)
> The other place you might want to update the amount of time a task has consumed is immediately after the CPU changes from user-space code to kernel code and immediately before the CPU changes from kernel code to user-space code
https://wiki.osdev.org/Brendan's_Multi-tasking_Tutorial
there's a lot of buzzwords that I need to look up
this is interesting
ooooh *learning noises*
hmm wondering if you could craft a process that will not wait for anything and just block forever
wait that's just a `while(true){}` so how does it switch if that's the case :think_bread: