From: Domen Puncer <domen@coderock.org>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Driver writer's guide to sleeping
Date: Mon, 27 Jun 2005 16:56:48 +0200 [thread overview]
Message-ID: <20050627145648.GA28445@nd47.coderock.org> (raw)
In-Reply-To: <200506251250.18133.vda@ilport.com.ua>
On 25/06/05 12:50 +0300, Denis Vlasenko wrote:
> Hi folks,
>
...
> msleep_interruptible(ms)
> Sleeps ms msecs (or more) unless has been woken up (signal, waitqueue...).
> Q: exact list of possible waking events? (I'm a bit overwhelmed by multitude
> of slightly different waitqueues, tasklets, softirqs, bhs...)
Only signal (or, obviously, timeout) will wake it. wake_up*() will not.
next prev parent reply other threads:[~2005-06-27 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-25 9:50 [RFC] Driver writer's guide to sleeping Denis Vlasenko
2005-06-25 11:29 ` Oliver Neukum
2005-06-25 11:54 ` Denis Vlasenko
2005-06-26 19:38 ` Oliver Neukum
2005-06-27 13:20 ` Denis Vlasenko
2005-06-27 14:56 ` Domen Puncer [this message]
2005-06-27 16:04 ` Nish Aravamudan
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=20050627145648.GA28445@nd47.coderock.org \
--to=domen@coderock.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
/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.