From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30617 invoked by alias); 16 Apr 2007 09:33:40 -0000 Received: (qmail 30602 invoked by uid 22791); 16 Apr 2007 09:33:39 -0000 X-Spam-Check-By: sourceware.org Received: from njclavin1.bloomberg.net (HELO njclavin1.bloomberg.net) (208.22.56.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 16 Apr 2007 10:33:36 +0100 Received: from ns11.bloomberg.com ([160.43.8.220] [160.43.8.220]) by njclavin1.bloomberg.net with ESMTP; Mon, 16 Apr 2007 05:33:34 -0400 Received: from ny2570-dr.corp.bloomberg.com ([172.20.193.211]) by ns11.bloomberg.com (8.11.7p1+Sun/8.10.2) with ESMTP id l3G9XXD07467; Mon, 16 Apr 2007 05:33:33 -0400 (EDT) Received: from ny2528-dr.corp.bloomberg.com (ny2528-dr.corp.bloomberg.com [172.20.193.160]) by ny2570-dr.corp.bloomberg.com (8.13.8/8.13.8) with ESMTP id l3G9XUH9032604; Mon, 16 Apr 2007 05:33:30 -0400 Received: from lo2525.corp.bloomberg.com ([172.16.16.57]) by ny2528-dr.corp.bloomberg.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 16 Apr 2007 05:33:30 -0400 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 16 Apr 2007 09:33:00 -0000 Message-Id: <4B24CC52E8A6EB4A95B414126492987C033482C9@lo2525.corp.bloomberg.com> In-Reply-To: <4690b0d10704130340y441a3580r7fd028969f55cc79@mail.gmail.com> References: <4690b0d10704130340y441a3580r7fd028969f55cc79@mail.gmail.com> From: "Chris Zimman" To: "M Arshad Khan" , X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: RE: [ECOS] minimum execution time with ecos X-SW-Source: 2007-04/txt/msg00071.txt.bz2 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 =3D get_timer_val(); ... tend =3D get_timer_val() elapsed =3D tend - tstart; } You may need to check for timer wraparound depending on what the timer resolution is. =20 --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 --=20 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