From: "David S. Miller" <davem@redhat.com>
To: wilson@whack.org
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: hires timestamps for netif_rx()
Date: Wed, 16 Jan 2002 17:08:52 -0800 (PST) [thread overview]
Message-ID: <20020116.170852.91311984.davem@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.40.0201161658260.28457-100000@apogee.whack.org>
In-Reply-To: <20020116.161759.68040363.davem@redhat.com> <Pine.GSO.4.40.0201161658260.28457-100000@apogee.whack.org>
From: Wilson Yeung <wilson@whack.org>
Date: Wed, 16 Jan 2002 17:03:58 -0800 (PST)
The discreprency is that get_fast_time() returns the current value of
xtime, while do_gettimeofday() may actually calculate the time and
consider both xtime and the jiffies.
Look at the x86 implementation of do_fast_time, it equals
do_gettimeofday() when TSC is present which is the only time
that do_gettimeofday is going to be more accurate than xtime.
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2002-01-17 1:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 19:56 CML2-2.1.4 is available Eric S. Raymond
2002-01-16 22:50 ` Ross Vandegrift
2002-01-16 22:43 ` Eric S. Raymond
2002-01-16 23:00 ` Ross Vandegrift
2002-01-16 23:01 ` Eric S. Raymond
2002-01-17 1:02 ` Ross Vandegrift
2002-01-17 1:51 ` [kbuild-devel] " Eric S. Raymond
2002-01-17 4:32 ` Eric S. Raymond
2002-01-16 23:33 ` hires timestamps for netif_rx() Wilson Yeung
2002-01-17 0:17 ` David S. Miller
2002-01-17 1:03 ` Wilson Yeung
2002-01-17 1:08 ` David S. Miller [this message]
2002-01-17 2:45 ` Wilson Yeung
2002-01-17 5:12 ` David S. Miller
2002-01-17 5:48 ` CM8338 hissing sound with linux kernel 2.4.6 to 2.4.17 vernie
2002-01-17 20:54 ` Thomas Cataldo
2002-01-17 19:15 ` hires timestamps for netif_rx() bill davidsen
2002-01-17 1:23 ` Andi Kleen
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=20020116.170852.91311984.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=wilson@whack.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