Performance is basically the same (in microbenchmarks), they went as far as preserving the use of red black trees for an apples to apples comparison, but it’s going to improve security as binder runs inside every process.

That means binder is going to join Asahi graphics, the Android Bluetooth stack, and puzzlefs in the serious drivers written in Rust club.

  • Quack Doc@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    This could be interesting, a bit worried how this will effect existing binder in distros and DKMS modules since waydroid relies on these

    • Tobu@lemmy.mlOP
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      1 year ago

      Distros will work a bit at shipping the right toolchain the first time they ship a rust-written module, but otherwise, it can’t break userspace. I guess they’ll start by merging the close reimplementation to make regressions easy to track.

    • Atemu@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      The C binder driver has been in the mainline kernel for one or two years at this point.

      • Quack Doc@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        just because its in mainline, doesnt mean distros build them though we are now seeing more and more distros use them, binder/fs being enabled is not a given