From: Matthew Wilcox <willy@debian.org>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: Grant Grundler <grundler@parisc-linux.org>,
Matthew Wilcox <willy@debian.org>,
parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Generic light-weight syscall.
Date: Mon, 28 Jul 2003 18:45:51 +0100 [thread overview]
Message-ID: <20030728174551.GC3840@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030728155703.GA32553@systemhalted>
On Mon, Jul 28, 2003 at 11:57:04AM -0400, Carlos O'Donell wrote:
> > Yes we can. We can sync CR16 across CPUs within a few CPU cycles.
> > I've described this before on parisc-linux.
>
> It might be too costly to do the sync'ing all the time, and too costly
> for a fast gettimeofday to do a sync at the polling point.
>
> > But all the boxes we support to date have exactly one clock source.
> > The multi-cell boxes (like superdome) will have multiple sources
> > and I don't know how to handle those - maybe a "not quite so fast"
> > gettimeofday().
>
>
> The whole point behind fast gettimeofday is that userspace apps that
> want to do timestamping on a _very_ accurate granularity (e.g.
> nanosecondes) can get monotically incrementing numbers on each
> gettimeofday. Do we even have such a fast clock on PA? What is the
> fastest clock across the most boxes?
You know, you don't even need kernel help for this. According to page
2-5 of the Kane book, the Interval Timer is accessible by non-privileged
instructions.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-07-28 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 6:37 [parisc-linux] Generic light-weight syscall Carlos O'Donell
2003-07-25 11:37 ` Matthew Wilcox
2003-07-26 17:48 ` Carlos O'Donell
2003-07-26 18:00 ` Carlos O'Donell
2003-07-27 12:27 ` Grant Grundler
2003-07-28 15:57 ` Carlos O'Donell
2003-07-28 17:45 ` Matthew Wilcox [this message]
2003-07-28 19:04 ` Carlos O'Donell
2003-07-28 19:14 ` Matthew Wilcox
2003-07-28 21:10 ` Richard Hirst
2003-07-29 17:50 ` Carlos O'Donell
2003-07-29 18:55 ` Grant Grundler
2003-07-29 21:06 ` Richard Hirst
2003-07-29 23:36 ` Carlos O'Donell
2003-07-30 16:37 ` Thibaut VARENE
2003-07-29 23:38 ` Carlos O'Donell
2003-07-29 18:51 ` Grant Grundler
2003-07-27 20:43 ` Michael S.Zick
2003-07-28 20:30 ` Randolph Chung
2003-07-28 20:37 ` Matthew Wilcox
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=20030728174551.GC3840@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=carlos@baldric.uwo.ca \
--cc=grundler@parisc-linux.org \
--cc=parisc-linux@parisc-linux.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