Check out my first novel, midnight's simulacra!

Fast UNIX Servers: Difference between revisions

From dankwiki
Line 19: Line 19:
** Signals, perhaps being used for asynchronous I/O with descriptors (<tt>[[Linux APIs|signalfd(2)]]</tt> on Linux unifies these with socket descriptors; <tt>kqueue</tt> supports <tt>EVFILT_SIGNAL</tt> events)
** Signals, perhaps being used for asynchronous I/O with descriptors (<tt>[[Linux APIs|signalfd(2)]]</tt> on Linux unifies these with socket descriptors; <tt>kqueue</tt> supports <tt>EVFILT_SIGNAL</tt> events)
** Timers (<tt>[[Linux APIs|timerfd(2)]]</tt> on Linux unifies these with socket descriptors; <tt>kqueue</tt> supports <tt>EVFILT_TIMER</tt> events)
** Timers (<tt>[[Linux APIs|timerfd(2)]]</tt> on Linux unifies these with socket descriptors; <tt>kqueue</tt> supports <tt>EVFILT_TIMER</tt> events)
** [[Pthreads|Condition variables]] becoming available
** [[Pthreads|Condition variables]] and/or [[Pthreads|mutexes]] becoming available
** Filesystem events (<tt>[[Linux APIs|inotify(7)]]</tt> on Linux, <tt>EVFILT_VNODE</tt> with <tt>kqueue</tt>)
** Filesystem events (<tt>[[Linux APIs|inotify(7)]]</tt> on Linux, <tt>EVFILT_VNODE</tt> with <tt>kqueue</tt>)
** Networking events (<tt>[[netlink|netlink(7)]]</tt> (PF_NETLINK) sockets on Linux, <tt>EVFILT_NETDEV</tt> with <tt>kqueue</tt>)
** Networking events (<tt>[[netlink|netlink(7)]]</tt> (PF_NETLINK) sockets on Linux, <tt>EVFILT_NETDEV</tt> with <tt>kqueue</tt>)

Revision as of 02:36, 25 June 2009

Everyone ought start with Dan Kegel's classic site, "The C10K Problem" (still updated from time to time). Jeff Darcy's "High-Performance Server Architecture" is much of the same. Everything here is advanced followup material to these excellent works, and of course the books of W. Richard Stevens.

Queueing Theory

Event Cores

Edge and Level Triggering

  • Historic interfaces like POSIX.1g/POSIX.1-2001's select(2) and POSIX.1-2001's poll(2) were level-triggered
  • epoll (via EPOLLET) and kqueue (via EV_CLEAR) provide edge-triggered semantics

The Full Monty: A Theory of UNIX Servers

We must mix and match:

  • Many event sources, of multiple types and possibly various triggering mechanisms (edge- vs level-triggered):
    • Socket descriptors, pipes
    • File descriptors referring to actual files (these usually have different blocking semantics)
    • Signals, perhaps being used for asynchronous I/O with descriptors (signalfd(2) on Linux unifies these with socket descriptors; kqueue supports EVFILT_SIGNAL events)
    • Timers (timerfd(2) on Linux unifies these with socket descriptors; kqueue supports EVFILT_TIMER events)
    • Condition variables and/or mutexes becoming available
    • Filesystem events (inotify(7) on Linux, EVFILT_VNODE with kqueue)
    • Networking events (netlink(7) (PF_NETLINK) sockets on Linux, EVFILT_NETDEV with kqueue)
  • One or more event notifiers (epoll or kqueue fd)
  • One or more event vectors, into which notifiers dump events
    • kqueue supports vectorized registration of event changes, extending the issue
  • Threads

See Also

Retrieved from "https://nick-black.com/dankwiki/index.php?title=Fast_UNIX_Servers&oldid=548"