From: christophe barbe <christophe.barbe@inup.com>
To: linux-kernel@vger.kernel.org
Subject: IRQ and sleep_on
Date: Mon, 5 Feb 2001 13:38:37 +0100 [thread overview]
Message-ID: <20010205133837.A485@pc8.inup.com> (raw)
In-Reply-To: <20010205131154.I31876@pc8.inup.com>
In-Reply-To: <20010205131154.I31876@pc8.inup.com>; from christophe.barbe@inup.com on lun, fév 05, 200 1 at 13:11:54 +0100
I've missed the thread "avoiding bad sleeps" last week. I've had a similar problem and I would like to discuss the solution I've used to avoid it.
I want to wake up a sleeping process from an IRQ handler. In the process, if I use a interruptible_sleep_on(), I need first to restore flags (otherwise the process will sleep forever).
restore_flags(flags);
// <<== here IRQ handler possibly call wake_up()
interruptible_sleep_on(&my_queue);
If I first enable interrupts and then call sleep_on, sometimes (often) the wake_up is called (due to a pending interrupt) when the wait_queue is empty.
I've written a modified version of interruptible_sleep_on which takes an additionnal argument : flags to be restored.
my_interruptible_sleep_on(&my_queue, flags);
It seems to be ok. I've no more bad sleeps or more exactly rarely and that why I submit this to you. Is my way to do it correct ?
I've joined at the end of this mail the modified function.
Thanks,
Christophe Barbé
long my_interruptible_sleep_on_timeout(struct wait_queue **p, long timeout, unsigned long oflags)
{
unsigned long flags;
struct wait_queue wait;
current->state = TASK_INTERRUPTIBLE;
// SLEEP_ON_HEAD
wait.task = current;
write_lock_irq(&waitqueue_lock);
__add_wait_queue(p, &wait);
write_unlock(&waitqueue_lock);
restore_flags(oflags);
timeout = schedule_timeout(timeout);
// SLEEP_ON_TAIL
write_lock_irqsave(&waitqueue_lock,flags);
__remove_wait_queue(p, &wait);
write_unlock_irqrestore(&waitqueue_lock,flags);
return timeout;
}
--
Christophe Barbé
Software Engineer
Lineo High Availability Group
42-46, rue Médéric
92110 Clichy - France
phone (33).1.41.40.02.12
fax (33).1.41.40.02.01
www.lineo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2001-02-05 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010205131154.I31876@pc8.inup.com>
2001-02-05 12:38 ` christophe barbe [this message]
2001-02-05 12:59 ` IRQ and sleep_on Manfred Spraul
2001-02-05 16:53 ` christophe barbe
2001-02-06 14:28 ` Anton Blanchard
2001-02-05 12:48 ` David Woodhouse
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=20010205133837.A485@pc8.inup.com \
--to=christophe.barbe@inup.com \
--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