From: Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ping(8) faster than light (do_get_fast_time) (fwd)
Date: Fri, 10 Aug 2001 15:41:26 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805055@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805052@msgid-missing>
On Fri, 10 Aug 2001, David Mosberger wrote:
> >>>>> On Fri, 10 Aug 2001 15:15:56 +0200 (CEST), Martin Wilck <Martin.Wilck@fujitsu-siemens.com> said:
>
> Martin> The deeper reason is that on IA64, *do_get_fast_time()
> Martin> equals do_normal_gettime(), which simply returns xtime.
>
> This distinction doesn't make sense on ia64 because there is no
> (slow) gettimeofday() to begin with.
Then, unless I'm completely mistaken, time_init() should change the
pointer do_get_fast_time to use do_gettimeofday() rather than
do_normal gettime(). Unless this is done, get_fast_time()
will simply return xtime. Or am I overlooking something?
> Martin> 1) Is do_gettimeofday () too slow on IA64 to use it for
> Martin> do_get_fast_time() ?
>
> I have no idea what you mean here. On ia64 do_gettimeofday() returns
> xtime plus an itc based time offset.
Yes, but get_fast_time() doesn't (see above), and that's the function
that is called for getting timestamps for socket buffers.
Martin
--
Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
FSC EP PS DS1, Paderborn Tel. +49 5251 8 15113
next prev parent reply other threads:[~2001-08-10 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 13:15 [Linux-ia64] ping(8) faster than light (do_get_fast_time) (fwd) Martin Wilck
2001-08-10 15:34 ` David Mosberger
2001-08-10 15:41 ` Martin Wilck [this message]
2001-08-10 17:37 ` David Mosberger
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-105590698805055@msgid-missing \
--to=martin.wilck@fujitsu-siemens.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