No announcement yet.

Understanding The Stabilized, High-Performance SD-Bus Of Systemd 221

  • Filter
  • Time
  • Show
Clear All
new posts

  • Understanding The Stabilized, High-Performance SD-Bus Of Systemd 221

    Phoronix: Understanding The Stabilized, High-Performance SD-Bus Of Systemd 221

    With today's release of systemd 221 besides enabling KDBUS support being compiled in unconditionally, it also stabilizes the new SD-BUS...

  • #2
    Linux seems to thrive these days

    Multiple IPCs
    Multiple display servers

    When we'll remain with only one of each kind, we can be sure that it's the best since multiple options have been tried


    • #3
      Originally posted by Danny3 View Post
      Multiple IPCs
      Well, it's the same IPC protocol, D-Bus, just implemented by different libraries: one is Linux-centric (this new one), one is portable (the original), and one is designed for GObject. I don't see them competing here. D-Bus itself runs on all the same *nix IPC methods that already exist (and anything else, really, like TCP/IP). It's just higher level protocol on top of these.

      My first introduction to D-Bus was consuming it, via Python. It was a piece of cake. My first service was written in GObject, where the integration is astounding, especially if you use Vala,

      kdbus will be a terrific addition to the kernel, as it will make it easy for any kernel module to expose services that are easily consumed by any programming language. Even beginning programmers would find it trivial to use services exposed by kernel. Over time, it can do much to improve collaboration between kernel-mode and user-mode software.


      • #4
        dbus is good for desktop apps
        like music players or... idk, whatever has widgets
        primarily for OO programming
        so for it was made for

        nothing else


        • #5
          Originally posted by gens View Post
          dbus is good for desktop apps
          Right. It is the choice for communicating when one side is an end user facing application.
          The other side can be another end user facing application, services that provide functionality to the user, e.g. NetworkManager, Samba, CUPS, etc., and the couple of system component that need to report state changes to user facing software, e.g. udisks