mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda@ilport.com.ua>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Driver writer's guide to sleeping
Date: Mon, 27 Jun 2005 16:20:52 +0300	[thread overview]
Message-ID: <200506271620.52836.vda@ilport.com.ua> (raw)
In-Reply-To: <200506262138.03708.oliver@neukum.org>

On Sunday 26 June 2005 22:38, Oliver Neukum wrote:
> Am Samstag, 25. Juni 2005 13:54 schrieb Denis Vlasenko:
> > On Saturday 25 June 2005 14:29, Oliver Neukum wrote:
> > > On Sat, 25 Jun 2005, Denis Vlasenko wrote:
> > > 
> > > > schedule_timeout(timeout)
> > > > 	Whee, it has a comment! :)
> > > >  * %TASK_UNINTERRUPTIBLE - at least @timeout jiffies are guaranteed to
> > > >  * pass before the routine returns. The routine will return 0
> > [snip]
> > > > 	Thus:
> > > > 	set_current_state(TASK_[UN]INTERRUPTIBLE);
> > > > 	schedule_timeout(timeout_in_jiffies)
> > > > 
> > > > msleep(ms)
> > > > 	Sleeps at least ms msecs.
> > > > 	Equivalent to:
> > > > 	set_current_state(TASK_UNINTERRUPTIBLE);
> > > > 	schedule_timeout(timeout)
> > > 
> > > If and only if you are not on any waitqueue. You may not be interrupted
> > > by a signal, but you still can be woken with an explicit wake_up()
> > 
> > Like this?
> 
> Yes, but we have macros for that. You are supposed to use them.

Erm.. I meant "Shall we correct that comment then, like this?".
Comment is plain wrong now.
--
vda


  reply	other threads:[~2005-06-27 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-25  9:50 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 [this message]
2005-06-27 14:56 ` Domen Puncer
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=200506271620.52836.vda@ilport.com.ua \
    --to=vda@ilport.com.ua \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome