From: Thomas Gleixner <tglx@linutronix.de>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Alexander Shishkin <virtuoso@slind.org>,
Andrew Morton <akpm@linux-foundation.org>,
John Stultz <johnstul@us.ibm.com>,
Chris Friesen <chris.friesen@genband.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Davide Libenzi <davidel@xmailserver.org>
Subject: Re: [RFC][PATCH 1/4] clock_rtoffset: new syscall
Date: Fri, 29 Apr 2011 19:32:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1104291931200.3005@ionos> (raw)
In-Reply-To: <1303937755.1065.8.camel@zag>
Alexander,
On Wed, 27 Apr 2011, Kay Sievers wrote:
> On Wed, 2011-04-27 at 16:02 +0200, Thomas Gleixner wrote:
> > On Wed, 27 Apr 2011, Alexander Shishkin wrote:
> > The completely untested patch below should solve the same problem in a
> > sane way. Restricted to timerfd, but that really should be sufficient.
>
> > Subject: timerfd: Allow timers to be cancelled when clock was set
> > From: Thomas Gleixner <tglx@linutronix.de>
> > Date: Wed, 27 Apr 2011 14:16:42 +0200
>
> Seems to work fine for me here for the weird "cron timer" case, or the
> simple "desktop clock" use-case -- where we want to rely on the timer to
> let the process sleep as long as possible, but wake it up to recalculate
> the next wakeup in case anything has changed in the meantime.
is that sufficient to solve your problems as well?
Thanks,
tglx
next prev parent reply other threads:[~2011-04-29 17:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 14:36 [RFCv4] timerfd: add TFD_NOTIFY_CLOCK_SET to watch for clock changes 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
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 [this message]
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.02.1104291931200.3005@ionos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=chris.friesen@genband.com \
--cc=davidel@xmailserver.org \
--cc=johnstul@us.ibm.com \
--cc=kay.sievers@vrfy.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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
Powered by JetHome