Hi,

what happen when you call wake_up_interruptible and there are no task waiting on that wait queue right then.

But say after some time a task comes along and start waiting (after the wake_up_interruptible is called).
Would that task be not wait at all because there was a pending wake up

What i'm looking for is a mechanism where by any old wake if not acted upon are lost. so in the above mention case if a task come along and waits after a wake has been sent, it continues to wait until a next wake up is sent.

feel free to ask me if there is some more clarification required.

TIA

fundu




--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

On Tue, 11 May 2010 22:32:46 +0200, Fundu <fundu_1999 [at] yahoo.com> wrote:
> what happen when you call wake_up_interruptible and there are no task=
waiting on that wait queue right then.
>
> But say after some time a task comes along and start waiting (after t=
he wake_up_interruptible is called).
> Would that task be not wait at all because there was a pending wake u=
p

It will be waiting for another wake up.

> What i'm looking for is a mechanism where by any old wake if not acte=
d upon are lost.

Semahore may be a good option.

--
Best regards, _ _
| Humble Liege of Serenely Enlightened Majesty of o' \,=3D./ `o
| Computer Science, Micha=C5=82 "mina86" Nazarewicz (o o)
+----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)-- Ooo--
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie"=
in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs