From: Ingo Oeser <netdev@axxeo.de>
To: Octavian Purdila <opurdila@ixiacom.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
Patrick Ohly <patrick.ohly@intel.com>,
netdev@vger.kernel.org
Subject: Re: [RFC][PATCH 1/1] net: support for hardware timestamping
Date: Tue, 29 Jul 2008 20:27:01 +0200 [thread overview]
Message-ID: <200807292027.01727.netdev@axxeo.de> (raw)
In-Reply-To: <200807292110.45320.opurdila@ixiacom.com>
Hi Octavian,
Octavian Purdila schrieb:
> On Tuesday 29 July 2008, Ingo Oeser wrote:
> In here:
>
> net/netfilter/xt_time.c
>
> it seems that the skb->tstamp needs to be CPU time.
Yeah, but not being off more than half a second should be ok
even for that obscure use case.
If your objective is to measure time and relate it to wall clock time,
your host clock should be close to that using NTP without any problems :-)
> Frankly I don't care about that, but the tstamp is also used in other places
> like the IP and TCP code paths and I can't say that I barely understand that
> part :)
>
> But if it is ok to use any kind of monotonic increasing timestamp, that will
> solve my problem, indeed.
Great! :-)
Best Regards
Ingo Oeser
next prev parent reply other threads:[~2008-07-29 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 0:07 [RFC][PATCH 0/1] net: support for hardware timestamps Octavian Purdila
2008-07-29 0:08 ` [RFC][PATCH 1/1] net: support for hardware timestamping Octavian Purdila
2008-07-29 14:52 ` Patrick Ohly
2008-07-29 15:49 ` Octavian Purdila
2008-07-30 9:35 ` Patrick Ohly
2008-07-30 13:38 ` Octavian Purdila
2008-07-30 14:00 ` Patrick Ohly
2008-07-29 15:54 ` Stephen Hemminger
2008-07-29 16:11 ` Octavian Purdila
2008-07-29 17:30 ` Ingo Oeser
2008-07-29 18:10 ` Octavian Purdila
2008-07-29 18:27 ` Ingo Oeser [this message]
2008-07-30 8:51 ` Patrick Ohly
2008-07-30 9:34 ` Ingo Oeser
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=200807292027.01727.netdev@axxeo.de \
--to=netdev@axxeo.de \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.com \
--cc=patrick.ohly@intel.com \
--cc=shemminger@vyatta.com \
/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;
as well as URLs for NNTP newsgroup(s).