Re: [chrony-users] Clarification on running chronyd on a machine with too many n/w interfaces

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]


On Fri, Sep 25, 2020 at 08:43:28PM +0530, Abhijith Sethuraj wrote:
> Hello,
> 
> Would there be an issue with too many n/w interfaces on a box from a
> chronyd perspective? We just want this machine's chronyd to sync its system
> time and not act as an ntp server for other clients. Noting here that there
> are too many interfaces because of ipvs (courtesy of ipvsadm).

If not using HW timestamping, chronyd doesn't care about interfaces,
or how many are there.

> We also use hardware timestamping and on our normal machines we have this
> set to `hwtimestamp *`. Should this be changed to use the actual interface
> that chronyd uses to sync time or is it fine to keep the config as it is?

With a large number (e.g. thousands) of interfaces enabled by
'hwtimestamp *' there might be a small perfomance impact on chronyd
server. For a client it wouldn't matter.

But there might also be a small impact on networking performance on
any device that has HW timestamping enabled, as there is additional
data (the timestamps) that need to be transferred from the NIC, even
for packets that don't need them. But if those interfaces all use the
same networking device, it doesn't matter.

-- 
Miroslav Lichvar


-- 
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.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/