Linus is rather predictable in this regard. For him it is just business as usual and he is making no special rules for kdbus. If kdbus is getting mainlined, it is getting mainlined for exactly the same reasons as other kernel features. Linus's lieutenants that have knowledge in that particular domain have to gives their "thumbs up". It has has to be a user-driven feature that solves real world problems, though sometimes new features are given the benefit of doubt whether they will be widely used. Some serious commitment to maintaining any non-trivial feature is also a priority.
While Linus have always been pragmatic, he have always regarded speed and efficency as important features of the kernel, since it was those virtues that drove Linux development forward in the beginning. Theoretical advantages, especially speed related, have never really impressed him. The kdbus developers could have done their homework better in this regard.
Linus is _only_ giving his general intention of merging it. kdbus still have to pass every test that other prominent features have to go through.
On the other hand, Linus have now signaled several times, that general handwaving against kdbus isn't enough; it has to be actionable criticism before he bothers to listen.
-
Linus Is Looking Forward To Merging KDBUS, But Not Convinced By Performance
Phoronix: Linus Is Looking Forward To Merging KDBUS, But Not Convinced By Performance
With the new Linux kernel mailing list thread about the prospects of merging KDBUS into the mainline Linux kernel, Linus Torvalds has provided his thoughts on the matter for this controversial feature backed by systemd developers for trying to provide a high-performance, kernel-based IPC solution...
Leave a comment: