From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: wait queues
Date: Tue, 21 Apr 2015 17:05:01 +0200 [thread overview]
Message-ID: <20150421150500.GA4412@grml> (raw)
In-Reply-To: <55352BD5.9020506@mrbrklyn.com>
Hi!
On 12:39 Mon 20 Apr , Ruben Safir wrote:
> On 04/20/2015 11:23 AM, michi1 at michaelblizek.twilightparadox.com wrote:
> > I would not recommend that. There are already functions in linux/wait.h for
> > these purposes like wait_event_interruptible().
>
>
> can you do that in the kernel? The wait_event_interuptable creates wait
> queues?
No, wait_event_interuptable waits on an existing waitqueue. If you want to
create a waitqueue, call init_waitqueue_head().
-Michi
--
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
next prev parent reply other threads:[~2015-04-21 15:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 1:23 wait queues Ruben Safir
2015-04-20 1:48 ` Ruben Safir
2015-04-20 1:54 ` Fred Chou
2015-04-20 8:57 ` Ruben Safir
2015-04-20 15:23 ` michi1 at michaelblizek.twilightparadox.com
2015-04-20 16:39 ` Ruben Safir
2015-04-21 15:05 ` michi1 at michaelblizek.twilightparadox.com [this message]
2015-04-22 11:23 ` wait queues semiphores kernel implementations Ruben Safir
2015-04-22 16:49 ` michi1 at michaelblizek.twilightparadox.com
-- strict thread matches above, loose matches on Subject: below --
2015-04-19 10:20 wait queues Ruben Safir
2012-11-07 20:54 Wait Queues Andres Lagar-Cavilla
2012-11-08 3:22 ` Andres Lagar-Cavilla
2012-11-08 7:42 ` Keir Fraser
2012-11-08 15:39 ` Andres Lagar-Cavilla
2012-11-08 16:48 ` Keir Fraser
2000-12-11 15:43 Carlo Pagano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150421150500.GA4412@grml \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.