This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Suitability of eCos
- To: ecos-discuss at sources dot redhat dot com
- Subject: RE: [ECOS] Suitability of eCos
- From: Stenberg Björn <Bjorn dot Stenberg at elema dot siemens dot se>
- Date: Tue, 16 Jan 2001 13:06:51 +0100
- Reply-To: Björn Stenberg <bjorn at haxx dot se>
> 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/