Kdbus meets linux-kernel

I'm very much reminded of the situation with the tux in-kernel-HTTP-server around a decade ago.

There, putting HTTP in-kernel was proposed for reasons with much in common with those stated for kdbus.

In that case, the outcome was that over a period of some time, tux's goals were broken down into a (fairly small) set of very generic in-kernel functionality.

This was pleasantly win-win : not only was the generic functionality useful outside of HTTP-servers, from memory the result was better for HTTP usage also.

[A couple of other success stories of breaking out kernel-space primitives from complex user-space systems spring to mind also: X11 and pthreads.]