All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhltc@us.ibm.com>
To: Sbs <sbs.pub@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Doubt: Does RT patch reduce interrupt latency?
Date: Fri, 24 Jul 2009 15:07:46 -0700	[thread overview]
Message-ID: <4A6A30B2.5070709@us.ibm.com> (raw)
In-Reply-To: <4cd511390907241111x3c6c9bbcw25230775c34ba3e@mail.gmail.com>

Sbs wrote:
> Hi All,
> 
> (Sorry if I am asking this on a wrong list. Please let me know the
> correct list for this question)
> 
> We have a system which needs to be connected to a device that will
> produce an interrupt during every msec. So, we want interrupt
> latencies less than 1 msec (else we will miss interrupts). We tried
> measuring interrupt latencies with RT patch applied. However, the
> results that he got suggested that after applying patches, the worst
> case latency went up.

As I understand it, if you are doing your processing via interrupts, the 
your latency to start processing interrupts will increase on average 
with the PREEMPT_RT patch.  There is additional scheduling overhead 
involved, and as Sven pointed out, if you don't bump the prio of the 
interrupt you care about, you can see MUCH higher latencies.

The PREEMPT_RT patch adds things like the rt-mutex replacement of most 
spinlocks, which adds preemption points and enable Priority Inheritance 
within the kernel, but this is all geared towards enable real-time 
applications.  If you just want fast OS processing of interrupts, then 
mainline provides you with a nice non-preemptible kernel side interrupt 
implementation that won't be affected by things like applications :-)

Please slap me if I've misrepresented PREEMPT_RT somehow. (I'm sure no 
invitation is actually required ;-)


-- 
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team

  parent reply	other threads:[~2009-07-24 22:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 18:11 Doubt: Does RT patch reduce interrupt latency? Sbs
2009-07-24 19:04 ` Sven-Thorsten Dietrich
2009-07-26  3:21   ` Sbs
2009-07-26  4:23     ` Sven-Thorsten Dietrich
2009-07-24 22:07 ` Darren Hart [this message]
2009-07-26  6:28   ` Sbs
2009-07-27 10:47     ` Stefan Agner

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=4A6A30B2.5070709@us.ibm.com \
    --to=dvhltc@us.ibm.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=sbs.pub@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.