From: "Lee Revell" <rlrevell@joe-job.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: "Luong Ngo" <luong.ngo@gmail.com>,
"Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Sleeping thread not receive signal until it wakes up
Date: Wed, 7 Mar 2007 16:03:36 -0500 [thread overview]
Message-ID: <75b66ecd0703071303k24799f10ibc5c49dc69c5ee86@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0703071457060.13923@chaos.analogic.com>
On 3/7/07, linux-os (Dick Johnson) <linux-os@analogic.com> wrote:
> Interruptible_sleep_on is interruptible, but for your task to
> actually be awakened and your alarm handler to get some CPU,
> it needs to be scheduled. If the BKL (big kernel lock) is
> held, it won't be scheduled until it is released.
You can schedule while holding the BKL and it will be dropped and reacquired.
Lee
next prev parent reply other threads:[~2007-03-07 21:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 5:31 Luong Ngo
2007-03-07 13:19 ` linux-os (Dick Johnson)
2007-03-07 19:28 ` Luong Ngo
2007-03-07 20:08 ` linux-os (Dick Johnson)
2007-03-07 21:03 ` Lee Revell [this message]
2007-03-08 0:40 ` Luong Ngo
2007-03-08 0:28 ` Luong Ngo
2007-03-08 13:01 ` linux-os (Dick Johnson)
2007-03-08 13:53 ` Thomas Gleixner
2007-03-08 22:52 ` Luong Ngo
2007-03-09 14:58 ` Sergey Vlasov
2007-03-09 19:50 ` Luong Ngo
2007-03-07 20:20 ` Jan Engelhardt
2007-03-07 18:09 ` Sergey Vlasov
[not found] <fa.kb3wuhac4W+1DqK61+sKe9uZwto@ifi.uio.no>
[not found] ` <fa.cyXmbtXvYymKHdI0rEXZCxyk+KE@ifi.uio.no>
[not found] ` <fa.zPDT1vfJF5MjVXXQH/l+YSaLl84@ifi.uio.no>
[not found] ` <fa.HmQN7RhZNBRsiJYADMOsY8DL67k@ifi.uio.no>
[not found] ` <fa.PDmHwxZ3arhmED5SLuEONyxUlz4@ifi.uio.no>
[not found] ` <fa.ygLhZcCLgDxnwAYYVse/Xshr9IE@ifi.uio.no>
2007-03-09 1:10 ` Robert Hancock
2007-03-09 3:24 ` Luong Ngo
2007-03-09 3:45 ` Parav K Pandit
2007-03-10 0:10 ` Luong Ngo
2007-03-10 8:22 ` Sergey Vlasov
2007-03-10 10:54 ` Luong Ngo
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=75b66ecd0703071303k24799f10ibc5c49dc69c5ee86@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=luong.ngo@gmail.com \
/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
all inboxes | Powered by JetHome®