public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com
To: ecos-bugs@ecos.sourceware.org
Subject: [Issue 1001684] New: Cyg_RealTimeClock::dsr is taking too much time
Date: Wed, 10 Oct 2012 09:56:00 -0000	[thread overview]
Message-ID: <bug-1001684-13@http.bugzilla.ecoscentric.com/> (raw)

Please do not reply to this email. Use the web interface provided at:
https://bugzilla.ecoscentric.com/show_bug.cgi?id=1001684

           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
        AssignedTo: unassigned@bugs.ecos.sourceware.org
        ReportedBy: fserban@dover-pidg.com
         QAContact: ecos-bugs@ecos.sourceware.org
                CC: ecos-bugs@ecos.sourceware.org
             Class: Advice Request


Hello,

When Jonathan and Alex visited us last week, we discussed about one of our
problem.
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
debugger)

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!
Anthony

PS: eCos options: 
- CYGIMP_KERNEL_COUNTERS_SINGLE_LIST
- 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.


             reply	other threads:[~2012-10-10  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10  9:56 bugzilla-daemon [this message]
2012-10-10  9:57 ` [Issue 1001684] " bugzilla-daemon
2012-10-10 13:16 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2012-10-10  9:56 [Issue 1001684] New: " bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-1001684-13@http.bugzilla.ecoscentric.com/ \
    --to=bugzilla-daemon@ecoscentric.com \
    --cc=ecos-bugs@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).