Announcement

Collapse
No announcement yet.

KDBUS Kernel D-Bus Code Continues Advancing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

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

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    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...

    Comment


    • #3
      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.

      Comment


      • #4
        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





        Comment


        • #5
          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.

          Comment


          • #6
            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,
            _

            Comment

            Working...
            X