From: Ingo Molnar <mingo@elte.hu>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/13] hrtimer: round up relative start time
Date: Tue, 14 Feb 2006 08:41:51 +0100 [thread overview]
Message-ID: <20060214074151.GA29426@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.61.0602131208050.30994@scrub.home>
ok, lets go back to this one:
* Roman Zippel <zippel@linux-m68k.org> wrote:
> Let's assume a get_time() which simply returns xtime and so has a
> resolution of around TICK_NSEC. This means the real time when one
> calls get_time() is somewhere between xtime and xtime+TICK_NSEC.
> Assuming the real time is xtime+TICK_NSEC-1, get_time() will return
> xtime and a relative timer with TICK_NSEC-1 will expire immediately.
i agree that on systems where get_time() has a TICK_NSEC resolution,
such short timeouts are bad.
i dont agree with the fix though: it penalizes platforms where
->get_time() resolution is sane.
Ingo
next prev parent reply other threads:[~2006-02-14 7:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 1:09 [PATCH 01/13] hrtimer: round up relative start time Roman Zippel
2006-02-13 10:52 ` Thomas Gleixner
2006-02-13 11:25 ` Roman Zippel
2006-02-13 13:01 ` Ingo Molnar
2006-02-13 13:42 ` Roman Zippel
2006-02-13 14:44 ` Ingo Molnar
2006-02-13 15:49 ` Roman Zippel
2006-02-13 19:55 ` Ingo Molnar
2006-02-13 22:29 ` Roman Zippel
2006-02-14 7:41 ` Ingo Molnar [this message]
2006-02-14 10:18 ` Roman Zippel
2006-02-14 12:20 ` [patch] hrtimer: round up relative start time on low-res arches Ingo Molnar
2006-02-14 21:51 ` Thomas Gleixner
2006-02-15 0:30 ` Roman Zippel
2006-02-15 9:19 ` Ingo Molnar
2006-02-15 12:26 ` Roman Zippel
2006-02-15 20:43 ` john stultz
2006-02-16 14:10 ` Roman Zippel
2006-02-16 19:06 ` john stultz
2006-02-16 23:44 ` Roman Zippel
2006-02-17 0:28 ` john stultz
2006-02-17 15:02 ` Roman Zippel
2006-02-14 10:26 ` [PATCH 01/13] hrtimer: round up relative start time Thomas Gleixner
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=20060214074151.GA29426@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.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