public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] provide /proc/sal/itc_drift through AUX?
Date: Fri, 21 Mar 2003 17:49:14 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705284@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705273@msgid-missing>

>>>>> "Jes" = Jes Sorensen <jes@wildopensource.com> writes:

>>>>> "David" = David Mosberger <davidm@napali.hpl.hp.com> writes:
David> No, not at all.  I was simply suggesting to always use
David> gettimeofday().  The light-weight implementation of
David> gettimeofday() runs in ~130 cycles, which isn't much slower
David> than what you could do in user-level.

Jes> Ok, that makes it even simpler, I will do that then.

Thinking about this, I still think we need the patch for glibc-2.2 and
maybe glibc-2.3 for compiling with kernels < 2.5.x? Though I'd
probably just say we should take the hit for people using 2.4 kernels
with glibc-2.3. The fast syscall support isn't going into glibc-2.2.

I assume some of the BuzzwordCompliantServer packages from various
distributions are going to stick to glibc-2.2 and kernel-2.4.x for a
while.

Back to mangling glibc-2.3.

Cheers,
Jes


      parent reply	other threads:[~2003-03-21 17:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 21:39 [Linux-ia64] provide /proc/sal/itc_drift through AUX? Jes Sorensen
2003-03-19 23:54 ` David Mosberger
2003-03-20  2:06 ` Jes Sorensen
2003-03-20 19:57 ` David Mosberger
2003-03-20 23:55 ` Rich Altmaier
2003-03-21  0:43 ` David Mosberger
2003-03-21  2:04 ` Jes Sorensen
2003-03-21 17:49 ` Jes Sorensen [this message]

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=marc-linux-ia64-105590723705284@msgid-missing \
    --to=jes@wildopensource.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