From: gshan <gshan@alcatel-lucent.com>
To: Satyam Sharma <satyam.sharma@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bugs in __schedule()
Date: Tue, 26 Jun 2007 16:55:43 +0800 [thread overview]
Message-ID: <4680D48F.6070105@alcatel-lucent.com> (raw)
In-Reply-To: <a781481a0706260150q2c27ddcal9595ebe91ff844c2@mail.gmail.com>
Satyam Sharma wrote:
> On 6/26/07, gshan <gshan@alcatel-lucent.com> wrote:
>> Thanks, Satyam. So I can replace the tasklet with kernel thread?
>
> That depends on what you want to do ...
>
> [ BTW: I should correct a typo in my original reply -- I should've said
> "scheduling while atomic", and not "scheduling while interrupts disabled"
> because interrupts are _not_ disabled in bottom halves, and from your
> stack backtrace it was evident that a tasklet was executing. :-) ]
I mean kernel thread could sleep, but tasklet can't. If so, it meet my
requirements.
next prev parent reply other threads:[~2007-06-26 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 7:57 bugs in __schedule() gshan
2007-06-26 8:14 ` Alexey Dobriyan
2007-06-26 8:18 ` gshan
2007-06-26 8:18 ` Satyam Sharma
2007-06-26 8:20 ` gshan
2007-06-26 8:25 ` Satyam Sharma
2007-06-26 8:36 ` gshan
2007-06-26 8:50 ` Satyam Sharma
2007-06-26 8:55 ` gshan [this message]
2007-06-26 9:08 ` Satyam Sharma
2007-06-26 9:13 ` gshan
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=4680D48F.6070105@alcatel-lucent.com \
--to=gshan@alcatel-lucent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=satyam.sharma@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