Re: [chrony-users] Time offset on versions 3+ without hw timestamping

2017-10-11 Thread Miroslav Lichvar
On Wed, Oct 11, 2017 at 06:26:51PM +0200, Thibaut BEYLER wrote: > Thanks, that seems like an interesting solution for power-saving. So far i > disabled c-state and power management system-wide ( > using /dev/cpu_dma_latency and governors) which gives really good results > (more stable peer delay &

Re: [chrony-users] Time offset on versions 3+ without hw timestamping

2017-10-06 Thread Miroslav Lichvar
On Mon, Sep 11, 2017 at 03:58:07PM +0200, Thibaut BEYLER wrote: > Coming back to my isues with chrony 3 : I played a bit with cpu power > management recently, at first to figure out first my problem with PPS > sources, and found out that disabling the c-states would improve *drastically > *chrony

Re: [chrony-users] Time offset on versions 3+ without hw timestamping

2017-09-11 Thread Thibaut BEYLER
Yes it's better that way ! Did not realise we could use -h like this.. Coming back to my isues with chrony 3 : I played a bit with cpu power management recently, at first to figure out first my problem with PPS sources, and found out that disabling the c-states would improve *drastically *chrony

Re: [chrony-users] Time offset on versions 3+ without hw timestamping

2017-09-11 Thread Miroslav Lichvar
On Mon, Sep 11, 2017 at 02:00:06PM +0200, Thibaut BEYLER wrote: > Ok thanks, I tried with 'local" before and got very bad results, did some > digging and turns out that was because I was having the same driftfile on > both instance (probably the parameter isn't necessary on the server > config),

Re: [chrony-users] Time offset on versions 3+ without hw timestamping

2017-09-11 Thread Thibaut BEYLER
Ok thanks, I tried with 'local" before and got very bad results, did some digging and turns out that was because I was having the same driftfile on both instance (probably the parameter isn't necessary on the server config), it's better now. I specified a custom sock as bindcmdaddress for each

Re: [chrony-users] Time offset on versions 3+ without hw timestamping

2017-08-31 Thread Bill Unruh
It has been a while now and I do not entirely remember. I wrote my own interrupt handler module, which would grab the time immediately that it was called by the kernel to service the interrupt, so it was effectively the kernel that was servicing the timestamping. If I recall correctly I had two

Re: [chrony-users] Time offset on versions 3+ without hw timestamping

2017-08-31 Thread Miroslav Lichvar
On Wed, Aug 30, 2017 at 12:14:05PM -0700, Bill Unruh wrote: > > You could run a separate server instance of chronyd on a different > > port with HW timestamping for the monitoring client. It needs to > > support the interleaved mode to be able to get the server's HW > > transmit timestamps. > >

Re: [chrony-users] Time offset on versions 3+ without hw timestamping

2017-08-30 Thread Bill Unruh
William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273 Physics _|___ Advanced Research _| Fax: +1(604)822-5324 UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/ On Wed, 30 Aug 2017,

Re: [chrony-users] Time offset on versions 3+ without hw timestamping

2017-08-30 Thread Miroslav Lichvar
On Wed, Aug 30, 2017 at 08:07:41PM +0200, Thibaut BEYLER wrote: > The monitoring software run on another server and monitor the chrony > clients (which are operating as servers in that case) over NTP So the same timestamping combination that the client is using to synchronize its clock is used in

Re: [chrony-users] Time offset on versions 3+ without hw timestamping

2017-08-29 Thread Miroslav Lichvar
On Tue, Aug 29, 2017 at 06:29:18PM +0200, Thibaut BEYLER wrote: > My setup is pretty simple, linux boxes, one switch between everything. For > my tests I am also using a third-party software as monitoring, connected > via PTP and PPS on my timeservers, which does ntp polling (with hw >