All of lore.kernel.org
 help / color / mirror / Atom feed
From: uaca@alumni.uv.es
To: linux-kernel@vger.kernel.org
Subject: Re: How much we can trust packet timestamping
Date: Mon, 30 Dec 2002 14:01:48 +0100	[thread overview]
Message-ID: <20021230130148.GB1591@pusa.informat.uv.es> (raw)
In-Reply-To: <1041253743.13097.3.camel@irongate.swansea.linux.org.uk>

On Mon, Dec 30, 2002 at 01:09:03PM +0000, Alan Cox wrote:
> On Mon, 2002-12-30 at 11:28, uaca@alumni.uv.es wrote:
> > 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...
> 
> The packet can be timestamped by the hardware receiving as well as by
> the kernel netif_rx code. This is actually intentional and there is
> hardware that supports doing IRQ raise time sampling which the driver
> can then use to get very accurate data.

Thanks Alan

Anybody know about a Linux driver that supports doing IRQ raise time
sampling? any doc/pointer/suggestion would be greatly appreciated

Thanks in advance

	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 12:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-30 11:28 How much we can trust packet timestamping uaca
2002-12-30 13:09 ` Alan Cox
2002-12-30 13:01   ` uaca [this message]
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=20021230130148.GB1591@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.