From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Mitchell Tasman <tasman@bbn.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] A possible mis-interaction between CONFIG_PREEMPT and GPIO IRQ handling for ARM, leading to extreme latency
Date: Fri, 25 May 2012 14:20:14 +0200 [thread overview]
Message-ID: <4FBF78FE.3020300@xenomai.org> (raw)
In-Reply-To: <4FBF4E69.1010200@bbn.com>
On 05/25/2012 11:18 AM, Mitchell Tasman wrote:
> Gilles,
>
> On 05/22/2012 05:30 PM, Gilles Chanteperdrix wrote:
>> On 05/22/2012 11:22 PM, Mitchell Tasman wrote:
>>> I have applied the patch that you supplied, and find a dramatic
>>> reduction in the maximum latency experienced in servicing edge-triggered
>>> GPIO interrupts. In testing so far today with the new patch, I have not
>>> encountered a single instance of the sort of extreme latency that
>>> prompted my query to the mailing list.
>>>
>>> Might you consider applying the new patch to I-Pipe for ARM 2.6.38.8,
>>> and publishing a new revision of that patch set? This could be of
>>> significant benefit to those members of the Xenomai community that are
>>> presently using a 2.6.38.8 kernel on ARM platforms.
>>>
>>> You might also consider addressing/replacing the original "ipipe/arm:
>>> defer chained interrupts handling" patch that was applied to I-Pipe for
>>> ARM 3.0.13, if the new patch is relevant to that kernel as well.
>
>> Yes, that's the plan. I am just waiting for Jean-Pascal's result to
>> confirm that everything is fine.
>
> I thought I'd report that testing of
> adeos-ipipe-2.6.38.8-arm-1.18-06.patch plus the revised "IRQ Chaining"
> patch that you e-mailed continues to show a dramatic reduction in the
> maximum latency in servicing edge-triggered GPIO interrupts. Good news
> as well is that the load on the Linux domain (e.g. dohell vs. idle)
> appears to have much less effect on the latency in servicing such
> interrupts than was previously the case.
>
> I noticed that Jean-Pascal reported success as well, on 23 May.
>
> Thank you once again for your excellent support, and I very much look
> forward to the updated I-Pipe for ARM 2.6.38.8 patch set.
You are welcome. The patch should be done during the week-end.
--
Gilles.
next prev parent reply other threads:[~2012-05-25 12:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 0:31 [Xenomai] A possible mis-interaction between CONFIG_PREEMPT and GPIO IRQ handling for ARM, leading to extreme latency Mitchell Tasman
2012-05-22 7:40 ` Gilles Chanteperdrix
2012-05-22 8:07 ` Gilles Chanteperdrix
2012-05-22 8:34 ` [Xenomai] RE : " Jean-Pascal JULIEN
2012-05-22 8:51 ` Gilles Chanteperdrix
2012-05-22 11:52 ` [Xenomai] RE : " Jean-Pascal JULIEN
2012-05-22 12:38 ` Gilles Chanteperdrix
2012-05-22 13:23 ` [Xenomai] RE : " Jean-Pascal JULIEN
2012-05-22 13:33 ` Gilles Chanteperdrix
2012-05-22 21:22 ` [Xenomai] " Mitchell Tasman
2012-05-22 21:30 ` Gilles Chanteperdrix
2012-05-25 9:18 ` Mitchell Tasman
2012-05-25 12:20 ` Gilles Chanteperdrix [this message]
2012-05-29 7:20 ` Mitchell Tasman
2012-05-29 8:06 ` Gilles Chanteperdrix
2012-05-29 8:52 ` Mitchell Tasman
2012-06-07 7:44 ` Eric Eric
2012-06-07 8:21 ` Gilles Chanteperdrix
2012-06-07 8:34 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2012-05-22 15:50 Jean-Pascal JULIEN
2012-05-23 8:22 Jean-Pascal JULIEN
2012-05-23 17:05 ` Mitchell Tasman
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=4FBF78FE.3020300@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=tasman@bbn.com \
--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.