mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] periodic clocksource update
Date: Fri, 05 May 2006 19:44:11 -0700	[thread overview]
Message-ID: <1146883452.12414.63.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0604272159400.32445@scrub.home>

On Thu, 2006-04-27 at 23:40 +0200, Roman Zippel wrote:
> There are big differences. :)
> As I already mentioned it produces smaller code and I tried to make the 
> fast path as small as possible.
> I also updated the algorithm to be more robust, the subtle changes are in 
> the clocksource_bigadjust(), which does a bit more work to keep the clock 
> from oscillating.

Ok, I'd like to integrate the ideas from your clocksource_adjust()
method into what I currently have as make_ntp_adj().  However the code
is still difficult to grasp, for example, you have the constants 33, 32
and 31 there with no explanation of exactly why you're using differing
shift values. I'm just still really hesitant to add code that is so
difficult to read and understand. 

So I'll take another pass at optimizing my make_ntp_adj function, and
maybe you could do the same with respect to clarity and comments for
clocksource_adjust() and maybe we can meet halfway?

thanks
-john


      reply	other threads:[~2006-05-06  2:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-03 19:57 Roman Zippel
2006-04-07 19:18 ` john stultz
2006-04-27 21:40   ` Roman Zippel
2006-05-06  2:44     ` john stultz [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=1146883452.12414.63.camel@cog.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®