[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: TASK_UN/INTERRUPTIBLE

On Tue, 2003-07-01 at 11:56, Frank A. Uepping wrote:

> set_current_state(TASK_INTERRUPTIBLE):
> Does this mean that the process is going to sleep,
> but can be awaken by delivery of a signal?
> 
> set_current_state(TASK_UNINTERRUPTIBLE):
> Does this mean that the process is going to sleep,
> but can NOT be awaken by delivery of a signal?

Correct.

Of course, both of these set_current_state() calls need to be included
with putting the task on a wait queue and invoking the scheduler. I.e.,
setting the state does not explicitly put the task to sleep (in the
sense that it will wake up again) but just ensure it will not end up on
a runqueue.

	Robert Love


--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/