From: Thomas Gleixner <tglx@linutronix.de>
To: Richard Cochran <richardcochran@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, john stultz <johnstul@us.ibm.com>
Subject: Re: [PATCH 0/2] [RFC] posix clock tuning
Date: Thu, 9 Sep 2010 14:50:57 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1009091443250.2477@localhost6.localdomain6> (raw)
In-Reply-To: <20100909122156.GA2823@riccoc20.at.omicron.at>
On Thu, 9 Sep 2010, Richard Cochran wrote:
> From my point of view, the discussion is going round in circles. There
Sorry for coming late and adding more to the general confusion. :)
> seems to be agreement that supporting PTP hardware clocks is a good
> idea. The objections seem to be about the form of the API. In general,
> there are three avenues.
>
> 1. character device (like hpet)
> 2. posix clock api
> 3. sysfs
>
> Or possibly some combination of the three.
I fail to see the requirement for any of those. Either the hardware
clock is suitable as a clocksource for general consumption, then it
should just be used as a clock source. If it's not - e.g. because it's
too slow to access - then it just should serve as a reference in the
NTP style and steer the timekeeping into sync.
As I said in the other reply, I know that you want a global
synchronized clock aside of CLOCK_REALTIME, but that's an easy to
solve problem.
See my other reply for details.
Thanks,
tglx
next prev parent reply other threads:[~2010-09-09 12:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 9:27 Richard Cochran
2010-09-03 9:29 ` [PATCH 1/2] posix clocks: introduce a syscall for " Richard Cochran
2010-09-03 9:58 ` Richard Cochran
2010-09-04 14:06 ` Richard Cochran
2010-09-09 10:49 ` Thomas Gleixner
2010-09-09 13:34 ` Richard Cochran
2010-09-09 20:10 ` Thomas Gleixner
2010-09-09 21:16 ` Thomas Gleixner
2010-09-09 22:53 ` john stultz
2010-09-10 9:23 ` Richard Cochran
2010-09-09 21:01 ` john stultz
2010-09-09 21:31 ` Thomas Gleixner
2010-09-03 9:30 ` [PATCH 2/2] posix clocks: introduce a sysfs presence Richard Cochran
2010-09-09 22:19 ` john stultz
2010-09-09 23:00 ` Alan Cox
2010-09-10 9:31 ` Richard Cochran
2010-09-11 0:20 ` Greg KH
2010-09-04 17:23 ` [PATCH 0/2] [RFC] posix clock tuning Christoph Lameter
2010-09-04 17:48 ` Christian Riesch
2010-09-05 1:37 ` Christoph Lameter
2010-09-05 5:56 ` Richard Cochran
2010-09-05 1:47 ` Christoph Lameter
2010-09-05 6:22 ` Richard Cochran
2010-09-05 7:20 ` Richard Cochran
2010-09-05 23:13 ` Christoph Lameter
2010-09-06 7:09 ` Richard Cochran
2010-09-09 9:58 ` Thomas Gleixner
2010-09-09 12:21 ` Richard Cochran
2010-09-09 12:50 ` Thomas Gleixner [this message]
2010-09-09 15:02 ` Alan Cox
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=alpine.LFD.2.00.1009091443250.2477@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=johnstul@us.ibm.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
/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
all inboxes | Powered by JetHome®