| Re: [chrony-users] Re: Locking PPS refclock with NTP source |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Re: Locking PPS refclock with NTP source
- From: Chris Perl <cperl@xxxxxxxxxxxxxx>
- Date: Thu, 7 Sep 2017 09:32:21 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=8UH57nVlixTriOvmv5xOOkol3JJ/Km6A1Pe6PrP4MBM=; b=yczzk2Zd6rCYJc+wvtIo1UvmZwcSPUhrJv2eJE8OszyoqtrbNW+wtmLSBYymAfqUQ9 WX6Q+9fKDr9uCfnPMIdmzAKLrCgm/FPV9i4bFq0p6LkYQuzUSo5pyn45uxULJcbUsWUs UOhv8LVjGn/RHEKJ//RxYNtKEsNLlMw2sE8lc=
On Thu, Sep 7, 2017 at 5:09 AM, Thibaut BEYLER <thibautbeyler@xxxxxxxxx> wrote:
> So i guess this is realted to some kind of cpu scheduling. However i
And, just to help rule out actual scheduler latency, you could run
chronyd with realtime priority (SCHED_FIFO or SCHED_RR) to make sure
it always has an absolute scheduling advantage over other processes
that aren't running with realtime priority.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.