mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: john stultz <johnstul@us.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] exponential update_wall_time
Date: Thu, 28 Sep 2006 23:11:50 +0200	[thread overview]
Message-ID: <20060928211150.GA32393@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0609282254450.6761@scrub.home>


* Roman Zippel <zippel@linux-m68k.org> wrote:

> > > add up to 1 second. Right now we slice it into HZ steps, but this 
> > > can be rather easily changed now.
> > 
> > Right off, it seems it would then make sense to make the ntp "ticks" 
> > one second in length. And set the interval values accordingly.
> > 
> > However, there might be clocksources that are incapable of running 
> > freely for a full second w/o overflowing. In that case we would need 
> > to set the interval values and the ntp tick length accordingly. It 
> > seems we need some sort of interface to ntp to define that base tick 
> > length. Would that be ok by you?
> 
> I don't see how you want to do this without some rather complex 
> calculations. I doubt this will make anything easier.

lets figure out a way to solve this in some manner - the loop of 
thousands of function calls on dynticks didnt look too well. Millions of 
kids will be grateful for it :-)

	Ingo

      reply	other threads:[~2006-09-28 21:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27 19:35 john stultz
2006-09-27 20:08 ` Ingo Molnar
2006-09-27 20:24   ` Thomas Gleixner
2006-09-27 22:05 ` Andrew Morton
2006-09-27 23:20   ` john stultz
2006-09-27 23:04 ` Roman Zippel
2006-09-27 23:13   ` john stultz
2006-09-27 23:40     ` Roman Zippel
2006-09-28  0:28       ` john stultz
2006-09-28 21:01         ` Roman Zippel
2006-09-28 21:11           ` Ingo Molnar [this message]

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=20060928211150.GA32393@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=johnstul@us.ibm.com \
    --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

Powered by JetHome