public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Chris Zimman" <czimman@bloomberg.com>
To: "M Arshad Khan" <marshadkhan@GMAIL.COM>,
	    <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] minimum execution time with ecos
Date: Mon, 16 Apr 2007 09:33:00 -0000	[thread overview]
Message-ID: <4B24CC52E8A6EB4A95B414126492987C033482C9@lo2525.corp.bloomberg.com> (raw)
In-Reply-To: <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

      parent reply	other threads:[~2007-04-16  9:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13 10:40 M Arshad Khan
2007-04-13 14:38 ` [ECOS] " Grant Edwards
2007-04-13 14:50   ` Grant Edwards
2007-04-16  9:33 ` Chris Zimman [this message]

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=4B24CC52E8A6EB4A95B414126492987C033482C9@lo2525.corp.bloomberg.com \
    --to=czimman@bloomberg.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=marshadkhan@GMAIL.COM \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).