This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: minimum execution time with ecos
- From: "Chris Zimman" <czimman at bloomberg dot com>
- To: "M Arshad Khan" <marshadkhan at GMAIL dot COM>, <ecos-discuss at sources dot redhat dot com>
- Date: Mon, 16 Apr 2007 10:33:25 +0100
- Subject: RE: [ECOS] minimum execution time with ecos
- References: <4690b0d10704130340y441a3580r7fd028969f55cc79@mail.gmail.com>
Arshad,
I'm not entirely sure I understand what you're asking, but I'll take a
shot at it anyhow.
If you need higher precision time, use your target CPUs built in timers
as these typically provide much higher resolution. If you want to
instrument routines to see their exact execution time, you can enable
profiling, or do something like:
my_func()
{
...
tstart = get_timer_val();
...
tend = get_timer_val()
elapsed = tend - tstart;
}
You may need to check for timer wraparound depending on what the timer
resolution is.
--Chris
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of M Arshad
Khan
Sent: 13 April 2007 11:40
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] minimum execution time with ecos
hii
can any body tell me wht is the minimum time delay that we can achive
with ecos.
i want to run a simulation on ecos that will run in less then a
tick(10mSec), is it possible and want to find its exact execution
time.. how to find that.
thanks
Arshad Khan
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss