public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Timer patches (nsec support + fastcalls for gettod/clock_gettime for all clocks)
Date: Mon, 12 Jul 2004 19:15:51 +0000	[thread overview]
Message-ID: <200407121215.51266.clameter@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0407091545250.5720@schroedinger.engr.sgi.com>

Have been working on the asm portion in the last days and also saw some 
strange things that could explain your problems (a segfault caused by 
clock_gettime and problems with seqlock handling). Will post another version 
later.

Thanks for the evaluation.
On Monday 12 July 2004 10:45 am, Chen, Kenneth W wrote:
> Christoph Lameter wrote on Friday, July 09, 2004 3:58 PM
>
> > The following patch is the first edition that is complete in that it
> > provides all existing functionality (fastcalls) and enhances various
> > interfaces:
> >
> > 1. Restructure timer interpolators to extract common code and provide a
> > structure that can be used from assembly language.
> > 2. Remove cmpxchg that causes scalability problems (for all clocks
> > including ITC now)
> >
> > 3. Simplify gettimeofday
> >
> > 4. Provide new fastcall gettimeofday suitable for all types of clock
> > (including cyclone and SN2 RTC). More than factor 10 speed gain on
> > machines that did not use ITC clock before.
> >
> > 5. Provide fastcall path for clock_gettime(CLOCK_REALTIME). Also for all
> > clock times. More than a factor 20 gain on this one since it returns
> > nanoseconds resolution and thereby avoids the multiplications / division
> > and the syscall overhead.
> >
> > 6. nanosecond resolution for CLOCK_REALTIME and CLOCK_MONOTONIC. This
> > yield a 40ns resolution on SN2.
> >
> > Todo:
> > - Test with cyclone machines
> > - Test with machines that only have ITC based clocks.
> >
> > Testind and feedback appreciated.
>
> The C portion works pretty well on ITC based clock.  One java benchmark
> that uses gettimeofday heavily gained one percentage point.  The assembly
> portion of the fsys call need some more work though, mingetty from the
> boot init script falls flat upon booting this patch.
>
> - Ken

  parent reply	other threads:[~2004-07-12 19:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-09 22:58 Timer patches (nsec support + fastcalls for gettod/clock_gettime Christoph Lameter
2004-07-12 17:45 ` Timer patches (nsec support + fastcalls for gettod/clock_gettime for all clocks) Chen, Kenneth W
2004-07-12 19:15 ` Christoph Lameter [this message]
2004-07-12 20:22 ` Christoph Lameter
2004-07-12 22:01 ` David Mosberger
2004-07-12 23:40 ` Timer patches (nsec support + fastcalls for gettod/clock_gettime Christoph Lameter
2004-07-12 23:48 ` David Mosberger
2004-07-13  1:19 ` Christoph Lameter

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=200407121215.51266.clameter@sgi.com \
    --to=clameter@sgi.com \
    --cc=linux-ia64@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