From: Thomas Gleixner <tglx@linutronix.de>
To: Scott James Remnant <scott@netsplit.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Shishkin <virtuoso@slind.org>,
linux-kernel@vger.kernel.org, Ken MacLeod <ken@bitsko.slc.ut.us>,
Shaun Reich <predator106@gmail.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Greg Kroah-Hartman <gregkh@suse.de>,
Feng Tang <feng.tang@intel.com>, Michael Tokarev <mjt@tls.msk.ru>,
Marcelo Tosatti <mtosatti@redhat.com>,
John Stultz <johnstul@us.ibm.com>,
Chris Friesen <chris.friesen@genband.com>,
Kay Sievers <kay.sievers@vrfy.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Artem Bityutskiy <dedekind1@gmail.com>,
Davide Libenzi <davidel@xmailserver.org>,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [RFCv4] timerfd: add TFD_NOTIFY_CLOCK_SET to watch for clock changes
Date: Fri, 11 Mar 2011 20:56:49 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1103112054540.2787@localhost6.localdomain6> (raw)
In-Reply-To: <AANLkTi=_DG8uYLxDnXF=so5daUE=w-pxL67mYaFAGkkL@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1967 bytes --]
On Fri, 11 Mar 2011, Scott James Remnant wrote:
> On Thu, Mar 10, 2011 at 12:25 AM, Andrew Morton
> <akpm@linux-foundation.org> wrote:
> > On Wed, 9 Mar 2011 18:01:09 -0800 Scott James Remnant <scott@netsplit.com> wrote:
> >
> >> > It would be helpful to know if the identified users of this feature
> >> > actually find it useful and adequate. __I guess the most common
> >> > application is the 1,001 desktop clock widgets. __Do you have any
> >> > feedback from any of the owners of those?
> >> >
> >> cron is another obvious one (or init systems attempting to replace
> >> cron). Having to wakeup and check the time every minute can be
> >> non-conducive to power savings, it would be better if we could just
> >> sleep until the next alarm and be woken up if the time changes in
> >> between.
> >>
> >> (That being said, we also need to poll for and/or check for timezone
> >> changes - but those are entirely userspace, so we can deal with that
> >> separately)
> >
> > Sure, there will be lots of applications.
> >
> > But what I'm asking isn't "it is a good feature". I'm asking "is the
> > feature implemented well". Ideally someone would get down and modify
> > cron to use the interface in this patch.
> >
> So I've just been thinking today - and I'm actually not sure whether
> this is needed at all for this case.
>
> A good cron implementation is going to set timers according to
> CLOCK_REALTIME; in the case where the clock changes forwards, those
> timers will fire as part of the clock changing already no? And in the
> case where the clock changes backwards, you don't want to re-run old
> ones anyway.
>
> Even the hourly/daily cases are actually at a fixed time, so would be
> triggered - and a decent implementation wouldn't trigger a given
> script more than once.
Yeah, I was wondering about today as well. Though when you set back
your clock several days, stuff might be surprised if it's not woken up
for several days :)
Thanks,
tglx
next prev parent reply other threads:[~2011-03-11 19:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 14:36 Alexander Shishkin
2011-03-10 0:25 ` Andrew Morton
2011-03-10 0:36 ` Kay Sievers
2011-03-10 8:19 ` Alexander Shishkin
2011-03-10 9:08 ` Thomas Gleixner
2011-03-10 11:16 ` Jamie Lokier
2011-03-10 11:41 ` Thomas Gleixner
2011-03-10 2:01 ` Scott James Remnant
2011-03-10 8:25 ` Andrew Morton
2011-03-11 19:51 ` Scott James Remnant
2011-03-11 19:56 ` Thomas Gleixner [this message]
2011-03-15 1:53 ` Scott James Remnant
2011-03-10 8:10 ` Alexander Shishkin
2011-03-10 8:02 ` Kirill A. Shutemov
2011-03-10 8:15 ` Alexander Shishkin
2011-03-10 8:48 ` Arnd Bergmann
2011-03-10 14:19 ` Alexander Shishkin
2011-03-10 9:52 ` Thomas Gleixner
2011-03-10 14:12 ` Alexander Shishkin
2011-03-10 14:55 ` Thomas Gleixner
2011-03-10 15:43 ` Alexander Shishkin
2011-03-10 16:40 ` Thomas Gleixner
2011-03-10 21:57 ` Thomas Gleixner
2011-04-27 10:43 ` [RFC][PATCH 1/4] clock_rtoffset: new syscall Alexander Shishkin
2011-04-27 10:43 ` [RFC][PATCH 2/4] hrtimer: add cancellation when clock is set Alexander Shishkin
2011-04-27 10:43 ` [RFC][PATCH 3/4] hrtimer: add nanosleep cancellation Alexander Shishkin
2011-04-27 10:43 ` [RFC][PATCH 4/4] timerfd: add cancellation Alexander Shishkin
2011-04-27 14:02 ` [RFC][PATCH 1/4] clock_rtoffset: new syscall Thomas Gleixner
2011-04-27 19:11 ` john stultz
2011-04-27 22:19 ` Thomas Gleixner
2011-04-27 20:55 ` Kay Sievers
2011-04-29 17:32 ` Thomas Gleixner
2011-05-02 8:10 ` Alexander Shishkin
2011-04-28 7:15 ` 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.LFD.2.00.1103112054540.2787@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=chris.friesen@genband.com \
--cc=davidel@xmailserver.org \
--cc=dedekind1@gmail.com \
--cc=feng.tang@intel.com \
--cc=gregkh@suse.de \
--cc=johnstul@us.ibm.com \
--cc=kay.sievers@vrfy.org \
--cc=ken@bitsko.slc.ut.us \
--cc=kirill@shutemov.name \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=mtk.manpages@gmail.com \
--cc=mtosatti@redhat.com \
--cc=predator106@gmail.com \
--cc=scott@netsplit.com \
--cc=viro@zeniv.linux.org.uk \
--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
Powered by JetHome