[ntp:questions] Re: Locking memory in ntp
David L. Mills
mills at udel.edu
Sun Sep 28 01:41:50 UTC 2003
One of the reasons the original burst mode was implemented in the first
place was the nasty surprise when the poll interval exceeded the router
ARP timeout. This happened with early Proteon routers which clobbered
the first NTP packet received in order to construct an ARP request in
the same buffer and then forgot about the NTP packet. Apparently,
everything old is new again.
Terje Mathisen wrote:
> Maarten Wiltink wrote:
> > Michael Sierchio wrote in message ...
> > <mlockall>
> >>IOW the only guaranteed way of locking all pages in physmem is
> >>to run without swap.
> > And the bulb lit up.
> > Is this standard procedure in real life NTP servers?
> A stratum-1 server will of course have enough RAM to never swap, a good
> stratum-2 server ditto.
> My S-2 servers also use burst mode against its primary inhouse S-1
> references, this handles the case where an ARP table entry have aged
> out, causing the first poll in a burst series to take significantly
> longer than the rest.
> - <Terje.Mathisen at hda.hydro.com>
> "almost all programming can be viewed as an exercise in caching"
More information about the questions