From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
Cc: Rodolfo Giometti <giometti@enneenne.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: LinuxPPS low-level IRQs timestamps & ldisc
Date: Mon, 2 Jun 2008 17:59:46 +0100 [thread overview]
Message-ID: <20080602175946.366c5d64@core> (raw)
In-Reply-To: <20080602170916.GD16164@csclub.uwaterloo.ca>
> Of course if you have to check of the DCD changed, that may not be
> constant. A check for whether this device currently has anyone that
> wants the timestamp though should be a constant time.
Not having to take the cost of that for other users is far more important
than a time variance of a jump prediction. CPU cache effects alone will
add way more variance already. It's not a meaningful number to chase
compared to the randomness introduced by the IRQ handling itself.
If you want perfect accuracy do what I²IT did years ago and use a card
which timestamps the physical IRQ bus transition and exposes it to the OS.
Alan
prev parent reply other threads:[~2008-06-02 17:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 16:15 LinuxPPS low-level IRQs timestamps & ldisc Rodolfo Giometti
2008-06-01 19:26 ` Lennart Sorensen
2008-06-02 6:51 ` Alan Cox
2008-06-02 9:25 ` Rodolfo Giometti
2008-06-02 14:02 ` Alan Cox
2008-06-02 14:56 ` Rodolfo Giometti
2008-06-02 15:48 ` Alan Cox
2008-06-02 17:22 ` Rodolfo Giometti
2008-06-02 19:35 ` Alan Cox
2008-06-02 20:21 ` Matti Aarnio
2008-06-03 13:40 ` Alan Cox
2008-06-02 17:09 ` Lennart Sorensen
2008-06-02 16:59 ` Alan Cox [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=20080602175946.366c5d64@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=giometti@enneenne.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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