This is the mail archive of the mailing list for the eCos project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Issue 1001684] New: Cyg_RealTimeClock::dsr is taking too much time

Please do not reply to this email. Use the web interface provided at:

           Summary: Cyg_RealTimeClock::dsr is taking too much time
           Product: eCos
           Version: 2.0
          Platform: Custom (Customer specific)
        OS/Version: Other
            Status: UNCONFIRMED
          Severity: normal
          Priority: normal
         Component: Kernel
             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?

Thank you!

PS: eCos options: 

Configure issuemail:
------- You are receiving this mail because: -------
You are the QA contact for the issue.
You are on the CC list for the issue.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]