From: Jan Kiszka <jan.kiszka@domain.hid>
To: rpm@xenomai.org
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Re: [patch, RFC] detect unhandled interrupts
Date: Wed, 30 Aug 2006 23:01:09 +0200 [thread overview]
Message-ID: <44F5FC95.4030206@domain.hid> (raw)
In-Reply-To: <1156971559.4323.82.camel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2405 bytes --]
Philippe Gerum wrote:
> On Wed, 2006-08-30 at 22:55 +0200, Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>> On Wed, 2006-08-30 at 20:50 +0200, Jan Kiszka wrote:
>>>> Philippe Gerum wrote:
>>>>
>>>>> On Wed, 2006-08-30 at 15:29 +0200, Jan Kiszka wrote:
>>>>>
>>>>>> Dmitry Adamushko wrote:
>>>>>>
>>>>>>> On 29/08/06, Jan Kiszka <jan.kiszka@domain.hid> wrote:
>>>>>>>
>>>>>>>> Dmitry Adamushko wrote:
>>>>>>>>
>>>>>>>> I think the additional costs of maintaining an error counter are almost
>>>>>>>> negligible. The test is in the unlikely path, and the first condition
>>>>>>>> already keeps us away from touching the counter.
>>>>>>>>
>>>>>>> But it's updated (unhandled = 0) any time the ISR(s) report something
>>>>>>> different from XN_ISR_NONE. Hence, it's at the beginning of the xnintr_t
>>>>>>> structure, hopefully, at the same cache line with other highly-used members
>>>>>>> (i.e. isr, cookie and hits).
>>>>>>>
>>>>>> Mmh, considering this and also the existing code I wonder if we could
>>>>>> optimise this a bit. I'm only looking at xnintr_irq_handler now (sharing
>>>>>> is slow anyway): currently the intr object is touched both before
>>>>>> (naturally...) and after the call to the ISR handler. Maybe we can push
>>>>>> all accesses before the handler for the fast path. E.g.:
>>>>>>
>>>>>> int unhandled = intr->unhandled;
>>>>>>
>>>>>> intr->unhandled = 0;
>>>>>> ++intr->hits;
>>>>>> s = intr->isr(...);
>>>>>>
>>>>>> if (s == XN_ISR_NONE) {
>>>>>> intr->unhandled = ++unhandled;
>>>>>> if (unhandled == XNINTR_MAX_UNHANDLED)
>>>>>> ALARM!
>>>>>> }
>>>>>>
>>>>>>
>>>>> Without speculating whether this could actually reduce cache misses or
>>>>> not when the branch is taken, the main issue I see here is that we would
>>>>> optimize the error case, at the expense of an additional memory fetching
>>>> No, it's the common path. Otherwise, I would have stopped already. I don't
>>>> expect further memory access because the head of intr should be cached
>>>> already.
>>>>
>>> Sorry, my brain cells must be glued together, but then, I just don't get
>>> what your patch actually optimizes :o}
>> Cache misses when accessing intr AFTER the ISR has finished (not on
>> latest Pentium with 4 MB caches...) for the non-error case.
>
> What do you call the "error case"?
>
XN_ISR_NONE
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2006-08-30 21:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 19:28 [Xenomai-core] [patch, RFC] detect unhandled interrupts Dmitry Adamushko
[not found] ` <44F496D7.60609@domain.hid>
2006-08-29 19:38 ` [Xenomai-core] " Dmitry Adamushko
2006-08-29 19:50 ` Jan Kiszka
2006-08-29 20:34 ` Dmitry Adamushko
2006-08-30 13:18 ` Philippe Gerum
2006-08-30 16:03 ` Dmitry Adamushko
2006-08-30 16:20 ` Gilles Chanteperdrix
2006-08-30 13:29 ` Jan Kiszka
2006-08-30 17:10 ` Dmitry Adamushko
2006-08-30 17:25 ` Dmitry Adamushko
2006-08-31 8:12 ` Dmitry Adamushko
2006-08-30 17:33 ` Jan Kiszka
2006-08-30 17:55 ` Philippe Gerum
2006-08-30 18:50 ` Jan Kiszka
2006-08-30 20:47 ` Philippe Gerum
2006-08-30 20:55 ` Jan Kiszka
2006-08-30 20:59 ` Philippe Gerum
2006-08-30 21:01 ` Jan Kiszka [this message]
2006-08-30 21:58 ` Philippe Gerum
2006-08-31 8:31 ` [Xenomai-core] " Philippe Gerum
2006-08-31 19:11 ` Jan Kiszka
2006-08-31 19:31 ` Philippe Gerum
2006-08-31 19:49 ` Jan Kiszka
2006-08-31 19:48 ` Philippe Gerum
2006-08-31 20:02 ` Dmitry Adamushko
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=44F5FC95.4030206@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=rpm@xenomai.org \
--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.