From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5808 invoked by alias); 10 Oct 2012 09:56:17 -0000 Received: (qmail 5784 invoked by uid 22791); 10 Oct 2012 09:56:15 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 10 Oct 2012 09:56:10 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id 6E43B2F78028 for ; Wed, 10 Oct 2012 10:56:09 +0100 (BST) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UnPQOQh9SEM9; Wed, 10 Oct 2012 10:56:04 +0100 (BST) From: bugzilla-daemon@ecoscentric.com To: ecos-bugs@ecos.sourceware.org Subject: [Issue 1001684] New: Cyg_RealTimeClock::dsr is taking too much time X-Bugzilla-Reason: QAcontact CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: eCos X-Bugzilla-Component: Kernel X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fserban@dover-pidg.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: normal X-Bugzilla-Assigned-To: unassigned@bugs.ecos.sourceware.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://bugzilla.ecoscentric.com/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Wed, 10 Oct 2012 09:56:00 -0000 Mailing-List: contact ecos-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-bugs-owner@sourceware.org X-SW-Source: 2012/txt/msg01292.txt.bz2 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.