On 09 Dec 2010, Marcel Holtmann wrote:
> I share the concern for the IO/CPU cost, but I don't think
> matters much in which daemon this is done. Especially if some slack
> is> allowed for the timers (which should be the case), ofonod will be
> scheduled when the CPU is anyways woken up (e.g. modem/audio interrupts
> wake up pulseaudio).
this is not really true. We can not wakeup ofonod every single second.
You might wanna start running powertop.
uhm, but I'm not claiming that. I was just stating that moving
the timers to e.g. pulseaudio in this case won't save much if
anything (the CPU will be woken up anyways, and the cost between
scheduling ofonod or a thread from PA, has really no difference
to overall consumption.. the CPU is woken up anyways and roughly
the same code to handle the timer is run).
So whether this code is in oFono or elsewhere, does not matter
much (to overall power consumption). The main question is of course
how often the counters are synced.
Personally I think the every-10sec interval is too short.
It's also highly system specific when wakeups start to get
too costly, so picking up one value seems difficult.