public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Dirk Husemann <hud@zurich.ibm.com>
To: "vasantha.rajan" <vasantha.rajan@cranessoftware.com>
Cc: mcmanis@mcmanis.com, ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] CYGNUM_HAL_RTC_PERIOD
Date: Wed, 22 Feb 2006 09:01:00 -0000	[thread overview]
Message-ID: <43FC2879.6060207@zurich.ibm.com> (raw)
In-Reply-To: <200602221019.24844.vasantha.rajan@cranessoftware.com>

[-- Attachment #1: Type: text/plain, Size: 1898 bytes --]

vasantha.rajan wrote:

>On Tuesday 21 February 2006 15:09, you wrote:
>
>Hi Dirk ,
>
>Thanks for your reply......
>
>In my previous mail I asked one more question.....but did'nt get reply.
>
>
>  
>
[...]

>         
> 1. I made  CYGNUM_HAL_RTC_DENOMINATOR to 100000, (so that my
> clock will trigger for 10us) and in my code if i initialize my alarm to
>cyg_alarm_initialize( alarm_hdl, 100000 + cyg_current_time(), 0 ), my alarm
> triggered for every 1 sec.
>
> If I reduce my value given to cyg_alarm_initialize() API to 10000 my alarm 
>triggered for every 0.1 sec ie, my code
> count value increments to 10 for every second and still if reduce my value
> to 1000 count value increments to 100 for every second,but if I still
> reduce my value to 100 ,I expected the count value should increment to
> 1000,but the count value increments upto some 350 approx.
>
> and if i still reduce my value to 10 or 1 my count only increments to 350
> only...why I am not getting the linear increment?????????
>  
>
my suspicion is that your system is increasingly busy/overloaded with 
doing interrupts and doesn't have enough cycles left to work through 
your thread's code...or in other words: you are using up your system's 
resources with servicing/trying to service the timer interrupts and you 
have no resources left for pretty much anything else.


-- 
Dr Dirk Husemann, Pervasive Computing, IBM Research, Zurich Research Lab
	hud@zurich.ibm.com --- http://www.zurich.ibm.com/~hud/
       PGP key: http://www.zurich.ibm.com/~hud/contact/PGP
  PGP Fingerprint: 983C 48E7 0A78 A313 401C  C4AD 3C0A 278E 6431 A149
	     Email only authentic if signed with PGP key.

Appended to this email is an electronic signature attachment. You can
ignore it if your email program does not know how to verify such a
signature. If you'd like to learn more about this topic, www.gnupg.org
is a good starting point.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 258 bytes --]

  parent reply	other threads:[~2006-02-22  9:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17 13:41 vasantha.rajan
2006-02-17 22:18 ` Chuck McManis
2006-02-21  5:10   ` vasantha.rajan
2006-02-21  7:54     ` Gary Thomas
     [not found]     ` <43FADFC7.90709@zurich.ibm.com>
     [not found]       ` <200602221019.24844.vasantha.rajan@cranessoftware.com>
2006-02-22  9:01         ` Dirk Husemann [this message]
2006-02-17 14:11 Àlex Bueno Guarner
2006-02-22  9:03 vasantha.rajan
2006-02-22  9:32 ` Andrew Lunn

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=43FC2879.6060207@zurich.ibm.com \
    --to=hud@zurich.ibm.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=mcmanis@mcmanis.com \
    --cc=vasantha.rajan@cranessoftware.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).