public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hendrik Wiese <7.e.Q@syncro-community.de>
To: Davide Rossetti <davide.rossetti@roma1.infn.it>
Cc: LKLM <linux-kernel@vger.kernel.org>
Subject: Re: Difference wait_event_interruptible and interruptible_wait_on
Date: Wed, 24 Nov 2004 14:42:26 +0100	[thread overview]
Message-ID: <41A48FC2.6010701@syncro-community.de> (raw)
In-Reply-To: <41A48CFB.2010304@roma1.infn.it>

Davide Rossetti wrote:

> Hendrik Wiese wrote:
>
>> Hello,
>>
>> I'm porting a device driver from 2.2.14 to 2.6.7 and I got some 
>> problems doing this...
>>
>> one of them is the following:
>> I know that a call to interruptible_wait_on puts a process into sleep 
>> state and that wait_event_interruptible does the same. But the 
>> difference is that wait_event_interruptible needs a condition to pass 
>> to wake up the processes. I do not need that mechanism since I wake 
>> up the processes at other places inside my driver with 
>> wake_up_interruptible calls. So how do I get a function similar to 
>> interruptible_wait_on where no condition is needed using kernel 2.6?
>
>
> I did not check, so maybe I'm wrong, anyway the condition 
> wait_event_interruptible is used to avoid the race window between the 
> time you decide to call it and the time the process is actually made 
> to sleep and ready to be woken up.
> regards
>
>
Thanks for your reply.

So what should such a condition be? What should be put there?

  reply	other threads:[~2004-11-24 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24 12:05 Difference wait_event_interruptible and interruptible_wait_on Hendrik Wiese
2004-11-24 13:30 ` Davide Rossetti
2004-11-24 13:42   ` Hendrik Wiese [this message]
2004-11-24 14:24     ` Arjan van de Ven
2004-11-25  8:37       ` Hendrik Wiese

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=41A48FC2.6010701@syncro-community.de \
    --to=7.e.q@syncro-community.de \
    --cc=davide.rossetti@roma1.infn.it \
    --cc=linux-kernel@vger.kernel.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