View Single Post
Old 08-16-2010, 10:27 AM   #6 (permalink)
needs more cowbell
dcb's Avatar
Join Date: Feb 2008
Posts: 5,038

pimp mobile - '81 suzuki gs 250 t
90 day: 96.29 mpg (US)

schnitzel - '01 Volkswagen Golf TDI
90 day: 53.56 mpg (US)
Thanks: 158
Thanked 267 Times in 210 Posts
Well it isn't technically "eaten up".
The way it is organized is that display updates are run in the main loop (low priority) every 1/2 second, and sensor updates happen in interrupts (and interrupt the main loop). If we get to the bottom of the main loop, where we sit and wait for the remainder of the 1/2 second, and we don't have any time left, then we would be at %100 indicated. So all the computations to display and interrupts are taking about 1/4 second if the cpu is at %50 and the rest is idle time, sort of (interrupts still happening)
  Reply With Quote
The Following User Says Thank You to dcb For This Useful Post:
NachtRitter (08-16-2010)