hi Jake,
Thanks for your response.
Not sure I follow here. You mean BC as in the boundary clock you're
connected to?
>> Yes.
You could possibly filter or average the delay to remove outliers, but I
am not sure how this impacts things. Other experts on this list are
probably better to answer that.
On 4/29/2021 8:04 AM, ramesh t wrote:
> hello Jake,
>
> Did time profiling using time ticks.
> Under the problem condition, observing clock_gettime of interface
> connected to BC is taking more time ticks. This results in phc offset
> jumping to 4 digit value momentarily. Also i'm not sure if r
hi Richard,
We have core pinned the ptp4l and phc2sys process to run on non system cores.
Do think chrt is required?
Please suggest.
Thanks for your support.
Regards,Ramesh
On Thursday, April 29, 2021, 08:45:26 PM GMT+5:30, Richard Cochran
wrote:
On Thu, Apr 29, 2021 at 03:04:07PM +000
On Thu, Apr 29, 2021 at 03:04:07PM +, ramesh t via Linuxptp-users wrote:
> Did time profiling using time ticks. Under the problem condition,
> observing clock_gettime of interface connected to BC is taking more
> time ticks. This results in phc offset jumping to 4 digit value
> momentarily. Al
hello Jake,
Did time profiling using time ticks. Under the problem condition, observing
clock_gettime of interface connected to BC is taking more time ticks. This
results in phc offset jumping to 4 digit value momentarily. Also i'm not sure
if reading across numa is triggering this issue.
Pleas
