[ntp:hackers] Patches to reinstate rank variable and add end keyword.

Paul Vixie paul at vix.com
Sat Aug 6 20:29:34 UTC 2005


# I haven't followed the politics here, but I am worried about the "old" bind
# 8 and the "new" bind 9. You say the bind 8 code is old but may have an
# asynchronous resolver, from which I gather bind 9 does not. Are we getting
# in a box here? It would really hurt if somewhere down the trail an awkward
# upgrade was necessary.

bind8's asynchrony framework is called "eventlib" and it's able to support
everything ntpd does now (hiding select() and win32 i/o completion ports)
while still supporting the development of a portable asynchronous resolver
(which i would write, if i thought anybody would use it.)  "eventlib" is
_not_ multiprocessor compatible.  if you expect to need more than one cpu,
you'll need threads, and you won't be able to use "eventlib".

bind9's asynchrony framework is called "taskmgr" and it can do everything
eventlib can do only more so... and it's compatible with threads.  the reason
bind9 has a different asynchrony framework is because of dnssec, which will
require more than one cpu.  otherwise bind9 would have used "eventlib" again.

i strongly believe that converting ntpd to use "eventlib" is the right thing.



More information about the hackers mailing list