From: Andrew Morton <akpm@osdl.org>
To: Paul Mackerras <paulus@samba.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org, johnstul@us.ibm.com
Subject: Re: [PATCH] Provide an interface for getting the current tick length
Date: Wed, 15 Feb 2006 19:11:46 -0800 [thread overview]
Message-ID: <20060215191146.126c052d.akpm@osdl.org> (raw)
In-Reply-To: <17395.59762.126398.423546@cargo.ozlabs.ibm.com>
Paul Mackerras <paulus@samba.org> wrote:
>
> > Can we share that code?
>
> We could share the code that computes time_adjust_step, i.e. this
> much:
>
> if ((time_adjust_step = time_adjust) != 0) {
> /*
> * We are doing an adjtime thing. Prepare time_adjust_step to
> * be within bounds. Note that a positive time_adjust means we
> * want the clock to run faster.
> *
> * Limit the amount of the step to be in the range
> * -tickadj .. +tickadj
> */
> time_adjust_step = min(time_adjust_step, (long)tickadj);
> time_adjust_step = max(time_adjust_step, (long)-tickadj);
> }
>
And the next line!
> Is that enough to be worth factoring out? Note that
> update_wall_time_one_tick() needs both time_adjust_step and
> delta_nsec, so to share more, we would have to have a function
> returning two values and it would start to get ugly.
>
update_wall_time_one_tick() gets:
long delta_nsec = new_function();
and your new function becomes
return (u64)new_function() << (SHIFT_SCALE - 10)) + time_adj;
next prev parent reply other threads:[~2006-02-16 3:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 1:17 [PATCH] Provide an interface for getting the current tick length Paul Mackerras
2006-02-16 1:35 ` Andrew Morton
2006-02-16 1:55 ` Paul Mackerras
2006-02-16 2:08 ` Andrew Morton
2006-02-16 2:54 ` Paul Mackerras
2006-02-16 3:11 ` Andrew Morton [this message]
2006-02-16 3:18 ` Paul Mackerras
2006-02-16 3:30 ` Linus Torvalds
2006-02-16 3:43 ` Paul Mackerras
2006-02-16 3:51 ` Linus Torvalds
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=20060215191146.126c052d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=torvalds@osdl.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.