From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Liu haixiang <liu.haixiang@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Question on Schedule and Preemption
Date: Tue, 18 Apr 2006 11:28:01 +0200 [thread overview]
Message-ID: <20060418092801.GC7258@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <1145352228.2976.18.camel@laptopd505.fenrus.org>
Hi,
On Tue, Apr 18, 2006 at 11:23:47AM +0200, Arjan van de Ven wrote:
>
> > If the current task is running and thus not yet exiting (!current->exit_state)
> > and is also in an atomic code section (i.e. under lock), it shouldn't call
> > any reschedule function (which also happens by just calling msleep(): use
> > mdelay() instead in that case!).
> >
>
> actually don't use mdelay, but change your code so that you CAN sleep :)
Ermm, I meant to say that, but forgot to do so clearly, sorry.
Basically long delays while holding locks are also a very baaad thing,
thus always avoid delays as much as possible there.
Andreas Mohr
--
No programming skills!? Why not help translate many Linux applications!
https://launchpad.ubuntu.com/rosetta
(or alternatively buy nicely packaged Linux distros/OSS software to help
support Linux developers creating shiny new things for you?)
next prev parent reply other threads:[~2006-04-18 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 7:23 Liu haixiang
2006-04-18 9:17 ` Andreas Mohr
2006-04-18 9:23 ` Arjan van de Ven
2006-04-18 9:28 ` Andreas Mohr [this message]
2006-04-18 12:55 ` Liu haixiang
2006-04-18 14:56 ` Steven Rostedt
2006-04-18 17:21 ` Liu haixiang
2006-04-18 17:32 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2006-04-18 13:31 Michael Guo
2006-04-18 7:12 Liu haixiang
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=20060418092801.GC7258@rhlx01.fht-esslingen.de \
--to=andi@rhlx01.fht-esslingen.de \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liu.haixiang@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®