All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Christoph Rohland <cr@sap.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Tigran Aivazian <tigran@veritas.com>,
	Mikael Pettersson <mikpe@csd.uu.se>, Jordan <ledzep37@home.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Error in x86 CPU capabilities starting with test5/6
Date: Fri, 17 Nov 2000 08:08:17 -0500	[thread overview]
Message-ID: <3A152DC1.21B35324@mandrakesoft.com> (raw)
In-Reply-To: <E13wkLK-0000bP-00@the-village.bc.nu> <qwwpujuvk1s.fsf@sap.com>

Christoph Rohland wrote:
> 
> Hi Alan,
> 
> On Fri, 17 Nov 2000, Alan Cox wrote:
> > Even checking the cpuinfo for the TSC should be done with care, and
> > its far far better to use gettimeofday unless doing very tiny
> > timings (eg for optimising code paths)
> 
> gettimeofday is _way_ to slow for a lot of every day uses. So
> applications will use rdtsc until we have some really fast
> (non-syscall) way to have high resolution time diffs.

IIRC, this came up a long time ago WRT Apache, which made a lot of
gettimeofday() calls.  Someone (Linus?) proposed the solution of a
'magic page' which holds information like gettimeofday() stuff, but
could be handled much more rapidly than a standard syscall.

-- 
Jeff Garzik             |
Building 1024           | The chief enemy of creativity is "good" sense
MandrakeSoft            |          -- Picasso
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-17 13:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-17  9:50 Error in x86 CPU capabilities starting with test5/6 Jordan
2000-11-17 11:39 ` Mikael Pettersson
2000-11-17 11:58   ` Tigran Aivazian
2000-11-17 12:10     ` Alan Cox
2000-11-17 12:51       ` Christoph Rohland
2000-11-17 13:08         ` Jeff Garzik [this message]
2000-11-17 13:21           ` Christoph Rohland
2000-11-17 13:31             ` Andi Kleen
2000-11-17 13:40               ` Jeff Garzik
2000-11-17 13:54                 ` Andi Kleen
2000-11-17 14:02                   ` Tigran Aivazian
2000-11-17 14:30                     ` Christoph Rohland
2000-11-17 14:50                       ` Alan Cox
2000-11-17 14:00                 ` Arjan van de Ven
2000-11-17 15:18         ` Andrea Arcangeli
2000-11-17 16:06           ` Christoph Rohland
2000-11-17 18:28             ` Andrea Arcangeli
2000-11-18  9:57               ` Christoph Rohland
2000-11-19 10:31               ` Albert D. Cahalan
2000-11-17 13:38       ` Mikael Pettersson
2000-11-17 12:04   ` Andi Kleen
2000-11-17 12:14     ` Jan Niehusmann
2000-11-17 12:22       ` Andi Kleen
2000-11-17 13:26 ` Mohammad A. Haque

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=3A152DC1.21B35324@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cr@sap.com \
    --cc=ledzep37@home.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=tigran@veritas.com \
    /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.