linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Timer task synchronization
Date: Tue, 03 Jun 2008 14:23:31 +0200	[thread overview]
Message-ID: <m2k5h6emgs.fsf@ohwell.denx.de> (raw)
In-Reply-To: 48401111.1060703@globaledgesoft.com

Hi Spoorthi,

>    I am dealing with timer synchronization problem.. we have two timer
> threads. The two timers are started one after the other. The first
> timer timeout value is 10s and the second timer tiemout value is 15s.
>
> The first timer fires after 10s and the timer thread is suspended
> until the second timer completes its task. once the second timer is
> done the first timer resumes.
>
> sometimes the first timer resumes back even before the second timer
> starts and blocks the second timer thread..

Reading your text, I have to admit, I have no idea whether you talk
about kernel threads, or posix threads and thus about kernel timers or
user space timers?

Without giving any more detail on what you try to do, and especially,
where you think the system does not behave as you would expect it,
nobody will be able to help you here.  Best of course is to show us some
stripped down code that exposes what you think is the problem.

Apart from that I guess that you somehow have synchronization problems
not directly related to timers at all, but that's just a gut feeling.

Cheers
  Detlev

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de

      reply	other threads:[~2008-06-03 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 14:37 Timer task synchronization Spoorthi KA
2008-06-03 12:23 ` Detlev Zundel [this message]

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=m2k5h6emgs.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --cc=linuxppc-embedded@ozlabs.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 NNTP newsgroup(s).