Posted Jul 29, 2004 14:47 UTC (Thu) by elanthis (guest, #6227)
[Link]
Basically, KGEM is a lot bigger and more complicated. KGEM has its own kernel<->userspace gateway (kevent uses netlink to get to userspace and is intended primarly for D-BUS to pick up the events), KGEM has its own datatype framework (kevent just sends a simple string), KGEM appears to support user->kernel events (kevent only allows sending events from kernel to userspace), KGEM is a hell of a lot of code (at least compared to kevents couple hundred), and KGEM is much more difficult to use (compared to the single simple function call required API of kevent).