From: george anzinger <george@mvista.com>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] linux-2.4.21-pre4_tsc-lost-tick_A0
Date: Thu, 30 Jan 2003 17:41:30 -0800 [thread overview]
Message-ID: <3E39D44A.95862534@mvista.com> (raw)
In-Reply-To: 1043976173.19558.12.camel@w-jstultz2.beaverton.ibm.com
john stultz wrote:
>
> On Thu, 2003-01-30 at 17:08, george anzinger wrote:
> > john stultz wrote:
> > > I'm already somewhat cautious that loops_per_jiffy isn't going to cut it
> > > with this patch (I'm thinking fast_gettimeoffset_quotient would probably
> > > be better). So please let me know if you find any issues with this
> > > patch.
> >
> > I think you are wondering about the "/", as am I. Possibly
> > a while loop, or, something like
> > fast_gettimeoffset_quotient, but scaled to do jiffies
> > instead of micro seconds. Still you SHOULD be doing this so
> > seldom that one wonders if the "/" is all that bad.
>
> Yea, I'm assuming it would be rare enough that the div won't be too much
> of a performance drop and would make the code more clear. Although if it
> is a concern I'm not opposed to speeding it up.
>
> > Another thing, possibly not so easily fixed given the
> > division between "arch" code and common code, but I would
> > like to see jiffies updated in only ONE place. With this
> > patch it is updated in .../kernel/timer.c AND in
> > .../arch/kernel/time.c. In the high-res-timers patch I made
> > the jiffies update an inline in an "arch" header file so I
> > could have the best of both worlds, i.e. update from common
> > code using arch resources (TSC, etc).
>
> Yea, I'm not psyched about that as well (not only is it updated twice,
> but three times: arch independent, tsc and cyclone). The inline bit
> sounds interesting, are you planning on pushing that in?
I am a bit discouraged on that front. I was hoping to get
the POSIX clocks & timers patch in, but it is long past
Halloween and, while he said he might, he didn't. I don't
know if he is finished as yet, but... The jiffies update
was part of the core patch to do the high res timers which
he said he would not take. I would like to try parting it
out and pushing in some stuff, such as scmath.h which makes
things like fast_gettimeoffset_quotient not only
understandable but easy. Folks in the cpu frequency area
would like that. Still, my boss has other plans...
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2003-01-31 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 0:17 [RFC][PATCH] linux-2.4.21-pre4_tsc-lost-tick_A0 john stultz
2003-01-31 1:08 ` george anzinger
2003-01-31 1:22 ` john stultz
2003-01-31 1:41 ` george anzinger [this message]
2003-01-31 20:19 ` john stultz
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=3E39D44A.95862534@mvista.com \
--to=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.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