From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil periodic thread does zero sleep()
Date: Sun, 22 Mar 2009 20:54:44 -0400 [thread overview]
Message-ID: <8755fbe09f6563d841971b95f67e365f@coraid.com> (raw)
In-Reply-To: <a5ec93342b820ee31072481987411c2f@gmx.de>
> The problem is that when sleep is a little bit too fast on every round,
> t will never catch up with ct. so it sleeps shorter and shorter until
> t - ct < 1.
>
> It all works when changing t += msec to t = ct + msec. It may still
> do a zero sleep, but the error will not add up.
why not just get rid of the double? then you will never zero sleep.
- erik
next prev parent reply other threads:[~2009-03-23 0:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 23:13 cinap_lenrek
2009-03-22 23:41 ` erik quanstrom
2009-03-23 0:16 ` cinap_lenrek
2009-03-23 0:24 ` erik quanstrom
2009-03-23 0:52 ` cinap_lenrek
2009-03-23 0:54 ` erik quanstrom [this message]
2009-03-23 4:04 ` ron minnich
2009-03-23 13:27 ` ron minnich
2009-03-23 0:24 ` cinap_lenrek
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=8755fbe09f6563d841971b95f67e365f@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@9fans.net \
/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).