This is the mail archive of the
mailing list for the eCos project.
[Issue 1001684] New: Cyg_RealTimeClock::dsr is taking too much time
- From: bugzilla-daemon at ecoscentric dot com
- To: ecos-bugs at ecos dot sourceware dot org
- Date: Wed, 10 Oct 2012 10:56:03 +0100
- Subject: [Issue 1001684] New: Cyg_RealTimeClock::dsr is taking too much time
- Auto-submitted: auto-generated
Please do not reply to this email. Use the web interface provided at:
Summary: Cyg_RealTimeClock::dsr is taking too much time
Platform: Custom (Customer specific)
Class: Advice Request
When Jonathan and Alex visited us last week, we discussed about one of our
We want to be determinastic with a high priority task that is woken up by a
timer DSR (by posting a semaphore)
The problem we are facing is that, sometimes the task is not awaken quickly
enough. There are some delay.
By using our debugger, I've seen that it is because Cyg_RealTimeClock::dsr
raises and takes too much time (I've attached the trace chart taken from our
In this attached screenshot, we see that we spent mainly time in
Cyg_RealTimeClock::dsr and in Cyg_ThreadTimer::alarm
In our current source code, we created one alarm (QF_alarm_handler) an we may
create a second one.
The question is, is it possible to put all the code in Cyg_RealTimeClock::dsr
in a task with a lower priority than our timer task, and only wake up this task
in the new Cyg_RealTimeClock::dsr?
Or maybe, you have some other advice to better fit our need?
PS: eCos options:
- CYGIMP_KERNEL_COUNTERS_SORT_LIST is not defined
Configure issuemail: https://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the issue.
You are on the CC list for the issue.