[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170427092809.GE5654@localhost>
Date: Thu, 27 Apr 2017 11:28:09 +0200
From: Miroslav Lichvar <mlichvar@...hat.com>
To: Richard Cochran <richardcochran@...il.com>
Cc: netdev@...r.kernel.org, Willem de Bruijn <willemb@...gle.com>,
Soheil Hassas Yeganeh <soheil@...gle.com>,
"Keller, Jacob E" <jacob.e.keller@...el.com>,
Denny Page <dennypage@...com>, Jiri Benc <jbenc@...hat.com>
Subject: Re: [PATCH v1 net-next 0/6] Extend socket timestamping API
On Wed, Apr 26, 2017 at 06:54:35PM +0200, Richard Cochran wrote:
> On Wed, Apr 26, 2017 at 04:50:29PM +0200, Miroslav Lichvar wrote:
> > This patchset adds new options to the timestamping API that will be
> > useful for NTP implementations and possibly other applications.
>
> Are there any userland ntp patches floating around to exercise the new
> HW time stamping option?
I'm not sure if anyone is working on support for HW timestamping in
ntp. With chrony, you can test it with an experimental code in the
hwts branch of https://github.com/mlichvar/chrony.
$ ./configure --enable-debug && make
# ./chronyd -d -d 'hwtimestamp *' 'server pool.ntp.org iburst' |& grep TIMESTAMP
TX SCM_TIMESTAMPING: swts=1493285228.512531924 hwts=0.000000000
TX SCM_TIMESTAMPING: swts=0.000000000 hwts=1493285226.073103885
SCM_TIMESTAMPING_PKTINFO: if=2 len=90
RX SCM_TIMESTAMPING: swts=1493285228.530657351 hwts=1493285226.091054104
TX SCM_TIMESTAMPING: swts=1493285230.553457791 hwts=0.000000000
TX SCM_TIMESTAMPING: swts=0.000000000 hwts=1493285228.113705104
SCM_TIMESTAMPING_PKTINFO: if=2 len=90
RX SCM_TIMESTAMPING: swts=1493285230.582817079 hwts=1493285228.142890229
--
Miroslav Lichvar
Powered by blists - more mailing lists