From: John Richard Moser <nigelenki@comcast.net>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gettimeofday(), clock_gettime(), timer_gettime()
Date: Wed, 26 Jul 2006 12:15:53 -0400 [thread overview]
Message-ID: <44C79539.4040506@comcast.net> (raw)
In-Reply-To: <p737j205r2q.fsf@verdi.suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andi Kleen wrote:
> John Richard Moser <nigelenki@comcast.net> writes:
>
>> - gettimeofday() is slow, or so they say, needing several milliseconds
>> to execute.
>
> It's not generally true, only sometimes. Please don't spread FUD.
>
http://lwn.net/Articles/192214/
"X is a big offender, apparently because the gettimeofday() call is
still too slow and maintaining time stamps with interval timers is faster."
Or so they say. I'm not the one spreading FUD; amusingly it takes me
50uS to run gettimeofday().
> -Andi
>
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
Creative brains are a valuable, limited resource. They shouldn't be
wasted on re-inventing the wheel when there are so many fascinating
new problems waiting out there.
-- Eric Steven Raymond
We will enslave their women, eat their children and rape their
cattle!
-- Bosc, Evil alien overlord from the fifth dimension
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIVAwUBRMeVNQs1xW0HCTEFAQImUg//eHXZfdTjazbLZFFUFVSoaCafunFzZyB5
uVmEq7yDWwsWe2jWTj9g3L/CpTECaiIAbcErrOxo8tGjN9PvGjKhfBTO8QmQAw6P
/InXa/DlPYN+ZhHAhXaNiS8CHMlVdSL6PT5NSMtugkepgRdQ4OhjOWe3MNgvSfdJ
tmUdq/clqz7S1gnPg8UvGOjgtUAlh+1+/7F/mYHgJn84DnexC81apVhP99jqvQ3o
u4dVyqxbfPIGkPDkZuorKY8HKeVLD6qettK8fK01pz2wgwSrjl1q+rZm2BGzuyMw
AAFtgfL/Z1DlEroaNcjAPJI3C43D4idGxpmtut/+sDP7wqxZ5LafULzotQWNbwDl
zi0MAfMbPkigPE8eUaQigHWTM7omvGFdadJhwx6Xd3ZmP2KTs6pCVU0X/A6i4ae/
fO1VbSztcVtoSy3Bz2jRIp4TjW1xuucdchjsT5yskpdEeeMwToKRV0qBTu1tyCv9
INQ4ovWNDsPgVLFx4l8EpcVlnYGelaJLNpzt+7bEFLsrW/q3thzCHFr440Cc5h4G
7Ukvu5s/a4BbMa6vnVPbaek7S8tBCrcHixzttJcjiObnxicZxr2V81sviVDMlCmy
zMuPeASzurgo2n3tDAmIwxICMUmsYB8l4oce7f1LLK9PFeOrVBhcLJymPCh8on4z
HIreAI1tj+Q=
=i75z
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-07-26 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 2:51 gettimeofday(), clock_gettime(), timer_gettime() John Richard Moser
2006-07-26 15:22 ` Andi Kleen
2006-07-26 16:15 ` John Richard Moser [this message]
2006-07-26 16:08 ` 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=44C79539.4040506@comcast.net \
--to=nigelenki@comcast.net \
--cc=ak@suse.de \
--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 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.