All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Keller, Jacob E" <jacob.e.keller@intel.com>
To: "Hall, Christopher S" <christopher.s.hall@intel.com>,
	"richardcochran@gmail.com" <richardcochran@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Stanton, Kevin B" <kevin.b.stanton@intel.com>,
	"Ronciak, John" <john.ronciak@intel.com>
Subject: Re: [PATCH] Add PTP cross-timestamp to the PTP driver interface
Date: Fri, 26 Jun 2015 15:24:25 +0000	[thread overview]
Message-ID: <1435332264.2160.3.camel@intel.com> (raw)
In-Reply-To: <20150626065507.GB1511@localhost.localdomain>

On Fri, 2015-06-26 at 08:55 +0200, Richard Cochran wrote:
> Chris,
> 
> Basically this patch looks okay to me.  Could you please add LKML,
> John Stultz and tglx (the time guys) onto CC?  I would like to get
> their Acks or at least let them have a chance to review it.
> 
> On Thu, Jun 25, 2015 at 04:42:56PM -0700, Christopher Hall wrote:
> > This patch allows system and device time ("cross-timestamp") to be 
> > performed 
> > by the driver. Currently, the timestamping is performed in the 
> > PTP_SYS_OFFSET 
> > ioctl.  It reads gettimeofday() and the gettime64() callback 
> > provided by the 
> > driver. The cross-timestamp is best effort ignoring the latency 
> > between the 
> > capture of system time (getnstimeofday()) and the device time 
> > (driver callback).
> 
> You can make the motivation more clear by mentioning how the newer
> PCIe spec foresees "perfect" timestamps.  If I didn't already know 
> the
> background, I would wonder who would ever want "best effort" single
> cross timestamps.
> 

FYI, I read "best effort" as a comment on how it's implemented today,
not what the implementation could provide.

> > Additionally, the callback, getsynctime64(), will only be called 
> > when 
> > n_samples == 1 because the driver returns only 1 cross-timestamp 
> > where 
> > multiple samples cannot be chained together.
> 
> There should be a way for user space to find out whether a particular
> device offers the cross timestamp capability.  There are reserved
> fields in 'struct ptp_clock_caps' that could be used.
> 

Yes, I agree. Otherwise we'd have to use only one sample in ptp4l in
order to benefit, but we'd be unable to tell it was worth it.

Regards,
Jake

> Thanks,
> Richard
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2015-06-26 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 23:42 [PATCH] Add PTP cross-timestamp to the PTP driver interface Christopher Hall
2015-06-25 23:42 ` [PATCH] Added additional callback to ptp_clock_info: Christopher Hall
2015-06-26  6:40   ` Richard Cochran
2015-06-26  6:55 ` [PATCH] Add PTP cross-timestamp to the PTP driver interface Richard Cochran
2015-06-26 15:24   ` Keller, Jacob E [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=1435332264.2160.3.camel@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=christopher.s.hall@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=kevin.b.stanton@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.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 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.