Re: Drivers that potentially leave state as TASK_{UN}INTERRUPTIBLE

From: David Woodhouse (dwmw2@infradead.org)
Date: Thu Sep 07 2000 - 11:18:07 EST

Next message: Linus Torvalds: "Re: [patch-2.4.0-test8-pre6] misc fixes"
Previous message: Eric Youngdale: "Weirdness in block device queues."
In reply to: George Anzinger: "Re: Drivers that potentially leave state as TASK_{UN}INTERRUPTIBLE"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

george@mvista.com said:
> > If there's other stuff on the run queue, it won't return immediately,
> > will it?

> It most likely will return immediately.

Oh well in that case it ought to task its task to something other than
TASK_RUNNING...

> > Otherwise, it would be TASK_UNINTERRUPTIBLE.
> UNINTERRUPTIBLE refers to being open to signals.

Indeed. That's what I want. I should have phrased it a little better.
"If I'm wrong about it not returning immediately, then it should be
TASK_UNINTERRUPTIBLE"

-- dwmw2

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/

Next message: Linus Torvalds: "Re: [patch-2.4.0-test8-pre6] misc fixes"
Previous message: Eric Youngdale: "Weirdness in block device queues."
In reply to: George Anzinger: "Re: Drivers that potentially leave state as TASK_{UN}INTERRUPTIBLE"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Sep 07 2000 - 21:00:30 EST