Do we need to call set_current_state (TASK
Yes, you must call set_current_state() before calling schedule(), because otherwise the scheduler will not remove the task from the run queue (if you just want to
Yes, you must call set_current_state() before calling schedule(), because otherwise the scheduler will not remove the task from the run queue (if you just want to
Generally speaking, uninterruptible sleep states are considered undesirable. Under normal circumstances, they cannot be triggered by user applications except by accident (e.g,
A process performing I/O will be put in D state (uninterruptable sleep), which frees the CPU until there is a hardware interrupt which tells the CPU to return to executing the
As you could read from that answer, setting the current process state to TASK_UNINTERRUPTIBLE is needed for make schedule() call, performed by that thread, to
When looking at the process with "ps ax" the stat column is "Dl" which means "uninterruptible sleep (usually IO)". Is it possible to find out more details on what the process is
I have a VirtualBox process hanging around which I tried to kill (KILL/ABORT) but without success. The parent pid is 1 (init). top shows the process as D which is documented as
PDF version includes complete article with source references. Suitable for printing and offline reading.