public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Stenberg Björn <Bjorn.Stenberg@elema.siemens.se>
To: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Suitability of eCos
Date: Tue, 16 Jan 2001 04:07:00 -0000	[thread overview]
Message-ID: <63E7EC6F3685D311B640080006279198022E7ECD@visbur.siemens.se> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

> 	But my application requires tick duration as low as a
> 100microseconds. I need to address such low time resolutions.

Don't confuse tick resolution with timer resolution. Many hardware platforms
for embedded use have timers with very high resolution. Many systems need
high-resolution timing. That does not mean you have to, or even should, run
your OS tick at those resolutions.

If you need a high-resolution timer, use one. It will send you an interrupt
precisely when you want it to and you can then act on it immediately.
Implement proper queueing/buffering/whatever there so your application can
handle the high data load in a controlled manner.

If you set your OS tick to a very high rate, your system will spend more
time in the kernel and have less time to do the actual work, and you may
ultimately find yourself with a performance problem.

-- 
Björn Stenberg
bjorn.stenberg@contactor.se
http://www.contactor.se/~bjst/

             reply	other threads:[~2001-01-16  4:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-16  4:07 Stenberg Björn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-16 11:08 Pamulapati, Indrasena (CTS)
2001-01-16  4:52 ` Jesper Skov
2001-01-16 11:26 ` Grant Edwards
2001-01-16  7:52 James Dabbs
2001-01-16  1:52 Pamulapati, Indrasena (CTS)
2001-01-16  2:44 ` Jesper Skov
2001-01-16  7:27 ` Grant Edwards
2001-01-16  1:27 Ramana
2001-01-16  1:10 Pamulapati, Indrasena (CTS)

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=63E7EC6F3685D311B640080006279198022E7ECD@visbur.siemens.se \
    --to=bjorn.stenberg@elema.siemens.se \
    --cc=ecos-discuss@sources.redhat.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).