From: Davide Libenzi <davidel@xmailserver.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Kyle Moffett <kyle@moffetthome.net>,
Alexander Shishkin <virtuoso@slind.org>,
Valdis.Kletnieks@vt.edu, LKML <linux-kernel@vger.kernel.org>,
John Stultz <johnstul@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Kay Sievers <kay.sievers@vrfy.org>, Greg KH <gregkh@suse.de>,
Chris Friesen <chris.friesen@genband.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [PATCHv6 0/7] system time changes notification
Date: Thu, 11 Nov 2010 18:35:51 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1011111813070.32375@davide-lnx1> (raw)
In-Reply-To: <alpine.LFD.2.00.1011112322280.2900@localhost6.localdomain6>
On Thu, 11 Nov 2010, Thomas Gleixner wrote:
> > [...]
> >
> > This would also enable the folks who want to support things like PHY
> > hardware clocks (for very-low-latency ethernet timestamping). It
> > would resolve the enumeration problem; instead of 0, 1, 2, ... as
> > constants, they would show up in sysfs and be open()able. Ideally you
> > would be able to set up ntpd to slew the "realtime" clock by following
> > a particular hardware clock, or vice versa.
>
> There are other plans for the various interesting clocks floating
> around which look pretty good.
>
> But what you folks really want for this stuff is an extension to
> timerfd as you want to be able to poll, right?
>
> So what about the following:
>
> Add a new flag TDF_NOTIFY_CLOCK_WAS_SET to the timerfd flags. Now this
> flag adds the timer to a separate list, which gets woken up when the
> clock is set.
What chu talkin bout Willis? :)
This borders the interface multiplexing, if I got your idea correctly.
Timerfd is about expiring private timers, not about getting out
notifications about system-wide time changes.
I understand your concerns about that code, but please do not use timerfd
as a sacrificial mule to fit something which IMO does not belong there.
- Davide
next prev parent reply other threads:[~2010-11-12 2:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 19:29 Alexander Shishkin
2010-11-11 19:29 ` [PATCHv6 1/7] notify userspace about time changes Alexander Shishkin
2010-11-11 20:55 ` Arnd Bergmann
2010-11-11 19:29 ` [PATCHv6 2/7] wire up sys_time_change_notify() on ARM Alexander Shishkin
2010-11-11 19:29 ` [PATCHv6 3/7] wire up sys_time_change_notify() on x86 Alexander Shishkin
2010-11-11 19:29 ` [PATCHv6 4/7] wire up sys_time_change_notify() on ia64 Alexander Shishkin
2010-11-11 19:30 ` [PATCHv6 5/7] wire up sys_time_change_notify() on s390 Alexander Shishkin
2010-11-11 19:30 ` [PATCHv6 6/7] wire up sys_time_change_notify() on powerpc Alexander Shishkin
2010-11-11 19:30 ` [PATCHv6 7/7] wire up sys_time_change_notify() on blackfin Alexander Shishkin
2010-11-11 20:28 ` [PATCHv6 0/7] system time changes notification Valdis.Kletnieks
2010-11-11 20:51 ` Alexander Shishkin
2010-11-11 21:16 ` Thomas Gleixner
2010-11-11 22:11 ` Kyle Moffett
2010-11-11 22:36 ` john stultz
2010-11-11 23:19 ` Kyle Moffett
2010-11-11 23:41 ` john stultz
2010-11-11 23:45 ` john stultz
2010-11-11 22:50 ` Thomas Gleixner
2010-11-12 2:35 ` Davide Libenzi [this message]
2010-11-17 19:06 ` Alexander Shishkin
2010-11-17 20:42 ` Davide Libenzi
2010-11-17 21:29 ` Alexander Shishkin
2010-11-17 21:34 ` Kay Sievers
2010-11-18 15:59 ` Alexander Shishkin
2010-11-17 21:46 ` Thomas Gleixner
2010-11-18 9:49 ` Alexander Shishkin
2010-11-18 13:08 ` Artem Bityutskiy
2010-11-12 9:25 ` Alan Cox
2010-11-12 10:53 ` Richard Cochran
2010-11-12 11:25 ` Alan Cox
2010-11-12 10:47 ` Kay Sievers
2010-11-12 12:30 ` Alexander Shishkin
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.DEB.2.00.1011111813070.32375@davide-lnx1 \
--to=davidel@xmailserver.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=chris.friesen@genband.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=johnstul@us.ibm.com \
--cc=kay.sievers@vrfy.org \
--cc=kirill@shutemov.name \
--cc=kyle@moffetthome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=virtuoso@slind.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
all inboxes | Powered by JetHome®