public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Houston <jim.houston@attbi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 64-bit jiffies, a better solution
Date: Sat, 11 May 2002 00:19:40 -0400	[thread overview]
Message-ID: <3CDC9BDC.F96F7C36@attbi.com> (raw)

Hi!

First what problem are you trying to solve?
Why not have both variables and if they happen
to endup in the same cache line you probably 
need years worth of jiffies to notice how
long one more add takes.  E.g.

	jiffies_64++;
	jiffies++;

To round out the list of options, how about a few lines of 
inline asm?  Maybe something like:

   extern unsigned long long jiffie_64;
   extern unsigned int jiffie;
   __asm__ (" \
        .data
        .align  8
        .global jiffie
        .global jiffie_64
        .type   jiffie,@object
        .size   jiffie,4
        .type   jiffie_64,@object
        .size   jiffie_64,8
   jiffie_64:
   jiffie:
        .long   0, 0
   ");

Adding the obvious ifdef of course.  Aside for broken
binutils this might be portable code :-)

Jim Houston - Concurrent Computer
Corp.

             reply	other threads:[~2002-05-11  4:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-11  4:19 Jim Houston [this message]
2002-05-11  6:58 ` 64-bit jiffies, a better solution george anzinger
  -- strict thread matches above, loose matches on Subject: below --
2001-10-23  5:10 How should we do a 64-bit jiffies? Keith Owens
2001-10-23  8:03 ` george anzinger
     [not found]   ` <200110231545.f9NFjgg01377@penguin.transmeta.com>
2002-05-10 21:35     ` 64-bit jiffies, a better solution george anzinger
2002-05-10 21:52       ` Linus Torvalds
2002-05-10 22:36         ` george anzinger
2002-05-10 22:40           ` Linus Torvalds
2002-05-13 11:09           ` Maciej W. Rozycki

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=3CDC9BDC.F96F7C36@attbi.com \
    --to=jim.houston@attbi.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