From: Peter Zijlstra <peterz@infradead.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
johnstul@us.ibm.com, davidel@xmailserver.org, virtuoso@slind.org,
tglx@linutronix.de, chris.friesen@genband.com,
kirill@shutemov.name, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:timers/core] timerfd: Allow timers to be cancelled when clock was set
Date: Wed, 11 May 2011 16:01:58 +0200 [thread overview]
Message-ID: <1305122518.2914.224.camel@laptop> (raw)
In-Reply-To: <BANLkTik5szBkinZEWySVjBKA5GF+6dn8Yg@mail.gmail.com>
On Wed, 2011-05-11 at 15:52 +0200, Kay Sievers wrote:
>
> No, fixed time spans have never been a problem, and are not the
> example here. It's about the normal wall clock, that wakes up every
> minute and updates the numbers on the screen.
'wakes up every minute' sounds like a fixed time interval to me.
Anyway, I still don't agree with the current implementation, its adding
overhead to timer fast-paths for a definite slow-path.
next prev parent reply other threads:[~2011-05-11 16:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-99ee5315dac6211e972fa3f23bcc9a0343ff58c4@git.kernel.org>
2011-05-11 10:23 ` [tip:timers/core] timerfd: Allow timers to be cancelled when clock was set Peter Zijlstra
2011-05-11 11:58 ` Kay Sievers
2011-05-11 13:45 ` Peter Zijlstra
2011-05-11 13:52 ` Kay Sievers
2011-05-11 14:01 ` Peter Zijlstra [this message]
2011-05-11 14:22 ` Kay Sievers
2011-05-11 14:30 ` Peter Zijlstra
2011-05-11 14:32 ` Kay Sievers
2011-05-11 14:48 ` Peter Zijlstra
2011-05-11 14:53 ` Kay Sievers
2011-05-11 15:11 ` Peter Zijlstra
2011-05-11 15:17 ` Kay Sievers
2011-05-11 15:31 ` Peter Zijlstra
2011-05-11 15:44 ` Kay Sievers
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=1305122518.2914.224.camel@laptop \
--to=peterz@infradead.org \
--cc=chris.friesen@genband.com \
--cc=davidel@xmailserver.org \
--cc=hpa@zytor.com \
--cc=johnstul@us.ibm.com \
--cc=kay.sievers@vrfy.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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 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.