From: Thomas Gleixner <tglx@linutronix.de>
To: Tim Sander <tstone@vlsi.informatik.tu-darmstadt.de>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Threaded Irqs (was "Changing Kernel thread priorities")
Date: Tue, 7 Jun 2011 23:56:47 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1106072345580.11814@ionos> (raw)
In-Reply-To: <201106072328.46186.tstone@vlsi.informatik.tu-darmstadt.de>
On Tue, 7 Jun 2011, Tim Sander wrote:
> Nevertheless are there still scheduling latencies for the usermode
> handler thread which then runs at rt prio 99 for about 1ms. I know
> this is not an preempt-rt kernel but i hoped to get better values out
> of this configuration.
>
> So if anybody has an idea how to get better latencies out of a 2.6.39
> kernel, please let me know.
The mainline forced irq thread handling is no guarantee for lower
latencies. We need to disable preemption via local_bh_disable() for
the forced threaded interrupts to satisfy the handler vs. softirq
assumptions. So you might get long lasting preempt disabled regions
due to long running interrupt handlers. Aside of that you still can
get long periods due to code which runs with preemption or interrupts
disabled. The forced threaded option has no way to change that.
It would be interesting to find the root cause for those >1ms
latencies. Tracing is your friend.
Thanks,
tglx
prev parent reply other threads:[~2011-06-07 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17185480.5304.1307435255996.JavaMail.root@WARSBL214.highway.tel ekom.at>
[not found] ` <17185480.5304.1307435255996.JavaMail.root@WARSBL214.highway.te lekom.at>
2011-06-07 8:32 ` Changing Kernel thread priorities Monica Puig-Pey
2011-06-07 8:43 ` Thomas Gleixner
2011-06-07 21:28 ` Threaded Irqs (was "Changing Kernel thread priorities") Tim Sander
2011-06-07 21:56 ` Thomas Gleixner [this message]
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=alpine.LFD.2.02.1106072345580.11814@ionos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tstone@vlsi.informatik.tu-darmstadt.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