From: Richard Cochran <richardcochran@gmail.com>
To: John Stultz <johnstul@us.ibm.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [RFC] Potential fix for leapsecond caused futex related load spikes
Date: Mon, 2 Jul 2012 12:16:08 +0200 [thread overview]
Message-ID: <20120702101606.GA16008@localhost.localdomain> (raw)
In-Reply-To: <4FF088B9.1000308@us.ibm.com>
On Sun, Jul 01, 2012 at 10:28:25AM -0700, John Stultz wrote:
>
> Reworking the patch now.
John,
I know you didn't like my (originally Michael Hack's) idea of keeping
time in TAI, but wouldn't changing to an internal, continuous time
scale (not necessary TAI) solve these sorts of timer issues?
There have been a number of clock/timer/leap bugs over the last
years. Some of these might have been avoided by using a continuous
scale, since no special timer actions would be needed during a leap
second.
The run time cost is low, just one additional test and addition when
reading the time. It might be worth it for the peace of mind when
the next leap second rolls around.
Thanks,
Richard
next prev parent reply other threads:[~2012-07-02 10:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-01 15:28 [PATCH] [RFC] Potential fix for leapsecond caused futex related load spikes Prarit Bhargava
2012-07-01 16:56 ` Prarit Bhargava
2012-07-01 17:28 ` John Stultz
2012-07-02 10:16 ` Richard Cochran [this message]
2012-07-02 16:58 ` John Stultz
2012-07-02 20:08 ` Sytse Wielinga
2012-07-03 9:23 ` Richard Cochran
2012-07-03 12:05 ` Sytse Wielinga
2012-07-03 13:41 ` Richard Cochran
-- strict thread matches above, loose matches on Subject: below --
2012-07-01 9:36 John Stultz
2012-07-01 9:42 ` John Stultz
2012-07-01 12:00 ` Jan Ceuleers
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=20120702101606.GA16008@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.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