From: p_ashish <priyadarshi.ashish@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: RT-Preemption is causing Very-High Interrupt Latency
Date: Sun, 17 Aug 2008 23:02:50 -0700 (PDT) [thread overview]
Message-ID: <19026358.post@talk.nabble.com> (raw)
I applied RT-preemption and High-Resolution Timer Patch to linux-2.6.19.2 .
It gave satisfactory result for 'cyclic_test' and
'HR-Timer clock-nanoSleep_test'.
But the problem is that Interrupt Latency in much more than before.
This is result which i got from my Interrupt Latency program.
WITH RT-preemption:
(Max Latency= 513.1 micro seconds and Min Latency= 12.1 micro seconds)
WITHOUT RT-preemption:
(Max Latency= 13.1 micro seconds and Min Latency= 1.8 micro seconds)
Since, RT-preemption implements ISR like threads, so is this the reason for
higher latency? Is there any way to improve this?
regards
~ashish
--
View this message in context: http://www.nabble.com/RT-Preemption-is-causing-Very-High-Interrupt-Latency-tp19026358p19026358.html
Sent from the linux-kernel mailing list archive at Nabble.com.
next reply other threads:[~2008-08-18 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 6:02 p_ashish [this message]
2008-08-18 10:00 ` RT-Preemption is causing Very-High Interrupt Latency Peter Zijlstra
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=19026358.post@talk.nabble.com \
--to=priyadarshi.ashish@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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