From: Alessio Sangalli <alesan@manoweb.com>
To: Iwo Mergler <iwo@call-direct.com.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: interrupt overhead on ARM architecture
Date: Tue, 29 Jul 2008 00:08:10 -0700 [thread overview]
Message-ID: <488EC1DA.7000708@manoweb.com> (raw)
In-Reply-To: <488EA477.7070101@call-direct.com.au>
Iwo Mergler wrote:
> In other words, you can't even measure the latency on a particular
> system and then assume it will stay anywhere near constant. Comparing
> different systems with the same processor core is hopeless.
Everything makes perfect sense. For this reason, I am willing to do some
tests on my own platform. How would you suggest to proceed? I would need
an extremely accurate way to measure time to begin with and then:
- read that time reference
- generate an interrupt by placing some data in a device or so
- reading again that time reference as first thing in the ISR
- save the result
- do the above in various scenarios, with different drivers enabled, CPU
load, etc etc
bye
Alessio
next prev parent reply other threads:[~2008-07-29 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 2:23 interrupt overhead on ARM architecture Alessio Sangalli
2008-07-29 5:02 ` Iwo Mergler
2008-07-29 7:08 ` Alessio Sangalli [this message]
2008-07-29 10:47 ` Benjamin Herrenschmidt
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=488EC1DA.7000708@manoweb.com \
--to=alesan@manoweb.com \
--cc=iwo@call-direct.com.au \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox