From: Anders Blomdell <anders.blomdell@domain.hid>
To: "Fernando Herrero Carrón" <elferdo@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Big differences in analogy interrupt handling time
Date: Fri, 16 Dec 2011 13:14:12 +0100 [thread overview]
Message-ID: <4EEB3614.4080805@domain.hid> (raw)
In-Reply-To: <CAMwkeZyxGbvYRzDGJucFd-1n4iALRQed5x+fMCVMTFzWYPvfnw@domain.hid>
On 12/16/2011 12:57 PM, Fernando Herrero Carrón wrote:
> [...]
>
>> Nice that somebody has already tested this.
>>
>
>
>> Nobody that has any insight on what might slow down execution with 20%
>> (curious mind wants to know)?
>>
>
> Dear Anders,
>
> I am afraid I don't understand your question. 20% with respect to what?
> Indeed, the "sync_dma" function performs some copy between kernel/user
> space. The old code performs exactly the same copy ten times, which
> multiplies the time spent in the interrupt handler tenfold, and adds 10us
> in idle wait. Besides that, I believe that the most time spent in an
> interrupt handler is in the i-pipe dispatching mechanism itself.
20% difference in execution time in identical code paths (attachment 'A'
and 'B'), where executing the same codepath in 'B' takes 20% longer time
than in 'A'
>
> There are for sure other people in the list more knowledgeable than me on
> this subject.
And me, obviously.
--
Anders Blomdell Email: anders.blomdell@domain.hid
Department of Automatic Control
Lund University Phone: +46 46 222 4625
P.O. Box 118 Fax: +46 46 138118
SE-221 00 Lund, Sweden
next prev parent reply other threads:[~2011-12-16 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 13:59 [Xenomai-help] Big differences in analogy interrupt handling time Anders Blomdell
2011-12-15 17:28 ` Fernando Herrero Carrón
2011-12-16 11:49 ` Anders Blomdell
2011-12-16 11:57 ` Fernando Herrero Carrón
2011-12-16 12:14 ` Anders Blomdell [this message]
2011-12-16 12:30 ` Fernando Herrero Carrón
2011-12-16 12:16 ` Fernando Herrero Carrón
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=4EEB3614.4080805@domain.hid \
--to=anders.blomdell@domain.hid \
--cc=elferdo@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.