public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.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:34:26 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805054@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805052@msgid-missing>

>>>>> 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.

  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.  The kernel is careful to return
only monotonically increasing time values, even in cases where the
ITCs in different CPUs are not perfectly synchronized.

  Martin> 3) If no, the ping(8) program on IA64 should IMO be changed
  Martin> to not use SO_TIMESTAMP (equivalent to "ping -U" with the
  Martin> RH7.1 ping).

We should first find out what the real problem is.  What timestamps
are present at the time ping is complaining?  If the earlier timestamp
is bigger than the later one, there is a bug somewhere.  If they're
equal (unlikely, given that we do ITC-based interpolation), ping
shouldn't complain.

	--david


  reply	other threads:[~2001-08-10 15:34 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 [this message]
2001-08-10 15:41 ` Martin Wilck
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-105590698805054@msgid-missing \
    --to=davidm@hpl.hp.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