All of lore.kernel.org
 help / color / mirror / Atom feed
From: uaca@alumni.uv.es
To: linux-kernel@vger.kernel.org
Subject: How much we can trust packet timestamping
Date: Mon, 30 Dec 2002 12:28:38 +0100	[thread overview]
Message-ID: <20021230112838.GA928@pusa.informat.uv.es> (raw)

Hi all

IMHO The problem is quite complicated because

+ common hardware is not designed for real time:

	- sends multiple PDUs within one interrupt, and can be delayed
	- Host adapter bus & infraestructure is not designed to garantee latency
  	etc...
     
+ software is also not designed for realtime

	- drivers may timestamp in softirq's
	- irqs has no deterministic latency either
	etc...

So even if do_gettimeofday() has 1/CPUfreq resolution by using TSC register
packet timestamping meassurement is biased, how much?

anybody has studied this? are there reports/doc about this topic?

of course, this can be avoided by using specialiced hardware, but I'm not
interested on that and I would like to know how much I can trust this
timestamps

Any comment would be greatly appreciated

Thanks

	Ulisses

                Debian GNU/Linux: a dream come true
-----------------------------------------------------------------------------
"Computers are useless. They can only give answers."            Pablo Picasso

--->	Visita http://www.valux.org/ para saber acerca de la	<---
--->	Asociación Valenciana de Usuarios de Linux		<---

             reply	other threads:[~2002-12-30 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-30 11:28 uaca [this message]
2002-12-30 13:09 ` How much we can trust packet timestamping Alan Cox
2002-12-30 13:01   ` uaca
2002-12-30 15:10     ` Alan Cox
2003-01-10 22:07   ` Werner Almesberger
2003-01-11  2:43     ` Alan Cox
2003-01-12 23:04       ` Werner Almesberger

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=20021230112838.GA928@pusa.informat.uv.es \
    --to=uaca@alumni.uv.es \
    --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.