From: Richard Cochran <richardcochran@gmail.com>
To: John Stultz <johnstul@us.ibm.com>,
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: Tue, 3 Jul 2012 15:41:34 +0200 [thread overview]
Message-ID: <20120703134134.GA19558@localhost.localdomain> (raw)
In-Reply-To: <20120703120535.GA30998@swielinga.nl>
On Tue, Jul 03, 2012 at 02:05:36PM +0200, Sytse Wielinga wrote:
> On Tue, Jul 03, 2012 at 11:23:25AM +0200, Richard Cochran wrote:
> > I think the established practice of announcing the event by network is
> > the only sane way of handling this issue. The list of TAI-UTC offsets
> > belongs to what David Mills has called our "institutional memory", and
> > this is a user space issue. The kernel's job is to just live in the
> > moment and provide the right time for *now*.
>
> I do suppose hardware clock and file system times will have to be UTC (or
> UTC-based local time) though?
Yes, you are right. Those things can never change. What I have in mind
is purely internal to the kernel and won't be visible in any way.
Thanks,
Richard
next prev parent reply other threads:[~2012-07-03 13:41 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
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 [this message]
-- 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=20120703134134.GA19558@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.