From: Miroslav Lichvar <mlichvar@redhat.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: netdev@vger.kernel.org, Willem de Bruijn <willemb@google.com>,
Soheil Hassas Yeganeh <soheil@google.com>,
"Keller, Jacob E" <jacob.e.keller@intel.com>,
Denny Page <dennypage@me.com>, Jiri Benc <jbenc@redhat.com>
Subject: Re: [PATCH v1 net-next 0/6] Extend socket timestamping API
Date: Thu, 27 Apr 2017 11:28:09 +0200 [thread overview]
Message-ID: <20170427092809.GE5654@localhost> (raw)
In-Reply-To: <20170426165435.GA21114@localhost.localdomain>
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
prev parent reply other threads:[~2017-04-27 9:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 14:50 [PATCH v1 net-next 0/6] Extend socket timestamping API Miroslav Lichvar
2017-04-26 14:50 ` [PATCH v1 net-next 1/6] net: define receive timestamp filter for NTP Miroslav Lichvar
2017-04-26 14:50 ` [PATCH v1 net-next 2/6] net: ethernet: update drivers to handle HWTSTAMP_FILTER_NTP_ALL Miroslav Lichvar
2017-04-26 14:50 ` [PATCH v1 net-next 3/6] net: add new control message for incoming HW-timestamped packets Miroslav Lichvar
2017-04-26 23:34 ` Willem de Bruijn
2017-04-27 10:15 ` Miroslav Lichvar
2017-04-27 11:38 ` Willem de Bruijn
2017-04-27 4:09 ` kbuild test robot
2017-04-26 14:50 ` [PATCH v1 net-next 4/6] net: don't make false software transmit timestamps Miroslav Lichvar
2017-04-26 14:50 ` [PATCH v1 net-next 5/6] net: allow simultaneous SW and HW transmit timestamping Miroslav Lichvar
2017-04-27 0:00 ` Willem de Bruijn
2017-04-27 16:17 ` Miroslav Lichvar
2017-04-27 16:21 ` Willem de Bruijn
2017-04-27 16:39 ` Miroslav Lichvar
2017-04-27 16:48 ` Willem de Bruijn
2017-04-28 8:54 ` Miroslav Lichvar
2017-04-28 15:50 ` Willem de Bruijn
2017-04-28 16:23 ` Miroslav Lichvar
2017-04-28 20:07 ` Willem de Bruijn
2017-05-02 9:56 ` Miroslav Lichvar
2017-04-26 14:50 ` [PATCH v1 net-next 6/6] net: ethernet: update drivers to make both SW and HW TX timestamps Miroslav Lichvar
2017-04-26 16:54 ` [PATCH v1 net-next 0/6] Extend socket timestamping API Richard Cochran
2017-04-27 9:28 ` Miroslav Lichvar [this message]
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=20170427092809.GE5654@localhost \
--to=mlichvar@redhat.com \
--cc=dennypage@me.com \
--cc=jacob.e.keller@intel.com \
--cc=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=soheil@google.com \
--cc=willemb@google.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).