It's been a while I haven't posted new ones. This morning, I was looking for some information on process and thread in computer science terms. There, I found some funny meaning regarding process states.
If a process needs to wait for a resource (wait for user input or file to open ...), it is assigned the "blocked" state. The process state is changed back to "waiting" when the process no longer needs to wait.
Why would that state go back to waiting if the process no longer needs to wait? Actually, it means it doesn't have to wait for the I/O process anymore and will wait the instructions from process scheduler or processor.
Wednesday 25 November 2009
Subscribe to:
Posts (Atom)