KDBUS Kernel D-Bus Code Continues Advancing
Phoronix: KDBUS Kernel D-Bus Code Continues Advancing
While KDBUS isn't yet ready for merging into the mainline Linux kernel, work on this kernel D-Bus implementation continues moving forward in step with systemd...
Or rather, it's unlikely that any form of Dbus will replace Binder at *any* point in the future, because they're fundamentally different beasts, designed for different purposes (async vs sync messages passing, etc). At least, that's the conclusion from the article...
Originally Posted by Phoronix
And now kdbus has decided to use the undocumented serialized format of GVarients as its transport protocol. Good luck getting any working independent implementations now.
I hope GKH is wrong about this b/c that was a motivating factor for kdbus. Obviously it's still very useful (especially in the infotainment space), but being able to get rid of Binder, and bring android that much closer to mainline would've been great.
Originally Posted by Delgarde
The overhead of kdbus seems not so much an issue anymore since arm devices are so much more powerful, and GKH has said that it shouldn't be difficult to emulate a syscall interface with kdbus, but the big problem is that binder is pretty damn complicated and only a few guys at google actually touch the code.
My interpretation from the discussion on the D-Bus list was that the format is being documented and will either end up as part of the D-Bus spec or reference from it.
Originally Posted by carewolf
But yes, it will be quite some time until it gets support in the D-Bus bindings that already implemented the serialization itself, i.e. are not using libdbus-1