From: "Eric S. Raymond" <esr@thyrsus.com>
To: tz <thomas@mich.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] Jitter and latency in a linux system might be a problem. Minimal BoM crosspost.
Date: Mon, 12 Mar 2012 17:08:31 -0400 [thread overview]
Message-ID: <20120312210831.GA17895@thyrsus.com> (raw)
In-Reply-To: <CAFv7Oih1+0hMRCJmRn33sy9O-NaYOjYVb-WKABd81yptvi1Wrg@mail.gmail.com>
tz <thomas@mich.com>:
> The PPS change detect thread in gpsd might have latency problems if
> the kernel is busy and/or it isn't a high priority - a plain userland
> program shows about 1mS jitter - a loop with the ioctl to block until
> a pin-change followed by gettimeofday will vary over about a 1000 uS
> band on my dual-core netbook. If you really need 100nS, you might
> need to use the kernel PPS, preferably with a dual core or better CPU
> so the interrupt can capture the nanosecond timer reliably.
We don't need 100ns. Our target accuracy is 1ms. This simplifies
things a lot.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
prev parent reply other threads:[~2012-03-12 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 19:09 tz
2012-03-12 20:44 ` Patrick Maupin
2012-03-12 21:02 ` tz
2012-03-12 21:22 ` Eric S. Raymond
2012-03-12 21:08 ` Eric S. Raymond [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=20120312210831.GA17895@thyrsus.com \
--to=esr@thyrsus.com \
--cc=thomas@mich.com \
--cc=thumbgps-devel@lists.bufferbloat.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