From: Florian Schmidt <mista.tapas@gmx.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: "linux-kernel @ vger. kernel. org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: possible bug in RP kernel
Date: Mon, 12 Sep 2005 11:14:24 +0200 [thread overview]
Message-ID: <20050912111424.1ae2f93e@mango.fruits.de> (raw)
In-Reply-To: <20050912090115.GA5731@elte.hu>
On Mon, 12 Sep 2005 11:01:15 +0200
Ingo Molnar <mingo@elte.hu> wrote:
> > 23 seconds gap between two wakeups
> >
> > Maybe my understanding of how sched fifo works is wrong, but i assumed
> > a higher prio thread shold get woken up from a sleep by the scheduler
> > which gets run by the timer interrupt [which is still non
> > preemptible].
>
> depending on what type of timeout you are using you'll also need to chrt
> the softirq-timer kernel thread(s) to prio 99. Otherwise the timer fn
> will have no chance to be executed. There's work going on by Thomas to
> make such things automatic, by prioritizing timers. If you have HRT
> enabled in the .config then it should mostly be automatic already
> though.
Ah,
thanks for the info. So it is a user (me) bug in the end :) This has
helped. Actually the code i had attached had another bug in it. But that
wasn't the responsible one.
Thanks again, and sorry for the multiple mails,
Florian Schmidt
--
Palimm Palimm!
http://tapas.affenbande.org
next prev parent reply other threads:[~2005-09-12 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050912105010.701a822f@mango.fruits.de>
2005-09-12 9:01 ` possible bug in RP kernel Ingo Molnar
2005-09-12 9:14 ` Florian Schmidt [this message]
2005-09-12 9:31 ` Ingo Molnar
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=20050912111424.1ae2f93e@mango.fruits.de \
--to=mista.tapas@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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