Results 1 to 6 of 6

Thread: KDBUS Kernel D-Bus Code Continues Advancing

  1. #1
    Join Date
    Jan 2007
    Posts
    13,456

    Default 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...

    http://www.phoronix.com/vr.php?view=MTU3MzI

  2. #2
    Join Date
    Apr 2010
    Posts
    669

    Default

    Quote Originally Posted by Phoronix
    t's unlikely that KDBUS will replace Android's Binder code in the near future.
    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...

  3. #3
    Join Date
    Nov 2012
    Posts
    112

    Default

    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.

  4. #4

    Default

    Quote Originally Posted by carewolf View Post
    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.
    There is plenty of documentation and you can always post in systemd-devel and ask if you need more help

    http://cgit.freedesktop.org/systemd/...-SERIALIZATION

    http://cgit.freedesktop.org/systemd/.../PORTING-DBUS1

    http://cgit.freedesktop.org/systemd/...md/DIFFERENCES

  5. #5
    Join Date
    Jan 2009
    Posts
    1,202

    Default

    Quote Originally Posted by Delgarde View Post
    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...
    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.
    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.

  6. #6
    Join Date
    Nov 2013
    Posts
    68

    Default

    Quote Originally Posted by carewolf View Post
    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.
    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.

    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

    Cheers,
    _

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •