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.
IPC standing for Inter Process Communication in this instance.
What else would it stand for?
It’s instructions per clock/cycle in a hardware context, because you can’t use clock speeds to compare performance between processors.
That is true…
Interastral Peace Corp
What about Intraastral Peace Corps?
Instructions per cycle
Was what I first read anyways
deleted by creator
I find it annoying when an article contains ATANE.
Clear case of DOTA.
This could be interesting, a bit worried how this will effect existing binder in distros and DKMS modules since waydroid relies on these
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.
The C binder driver has been in the mainline kernel for one or two years at this point.
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
