All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Tomas Kalibera <kalibera@domain.hid>
Cc: xenomai@xenomai.org, Jan Kiszka <jan.kiszka@domain.hid>
Subject: Re: [Xenomai-help] rt_intr_wait takes 10ms
Date: Sun, 25 May 2008 16:09:16 +0200	[thread overview]
Message-ID: <18489.29452.834191.596609@domain.hid> (raw)
In-Reply-To: <4838AC7A.7030609@domain.hid>

Tomas Kalibera wrote:
 > 
 > Hi,
 > 
 > I've measured interrupt latencies using irqbench and extended it a bit 
 > to measure also latencies of a user space task that uses "rt_intr_wait", 
 > as opposed to the specialized ioctl call used presently by the benchmark.
 > 
 > I found out that when the call to rt_intr_wait does not block (there is 
 > already an interrupt pending), the latency is nice, i.e. 20us. However, 
 > when rt_intr_wait blocks, the latency is 10ms (the whole quantum).
 > 
 > I thought that once the interrupt arrives and the kernel space header 
 > signals the interrupt, the Xenomai scheduler should be invoked and 
 > should preempt any presently running thread and immediately wake up the 
 > thread blocked in rt_intr_wait. Is this correct ?
 > 
 > The thread blocked in rt_intr_wait had maximum priority (99) and was in 
 > primary mode.
 > 
 > Interestingly, when I run the original version of the irqbench 
 > benchmark, even the user space version (-t 0, default) that waits for 
 > the interrupt using the specialized ioctl call, had nice latencies about 
 > 20us. Any ideas why the rt_intr_wait does not behave equally well ?

Did you check the interrupts count returned by rt_intr_wait ? What else
do you do in the loop calling rt_intr_wait ? Do not you use special
features such as I_NO_AUTOENA ?

-- 


					    Gilles.


      reply	other threads:[~2008-05-25 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-25  0:02 [Xenomai-help] rt_intr_wait takes 10ms Tomas Kalibera
2008-05-25 14:09 ` Gilles Chanteperdrix [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=18489.29452.834191.596609@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jan.kiszka@domain.hid \
    --cc=kalibera@domain.hid \
    --cc=xenomai@xenomai.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 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.