Re:“DBus is seriously screwed up”
by vezzy-fnord on Tuesday April 28, 2015 @09:16AM
(#9452011)
You're talking about memfd, I think? That has nothing to do with kdbus in particular. It's an independent syscall that replaces many use cases for splice/vmsplice, even though it was introduced as part of the kdbus project - it's still a separate thing.
Re:“DBus is seriously screwed up”
by the_mitsuhiko on Tuesday April 28, 2015 @10:33AM
(#9452634)
> You're talking about memfd, I think? That has nothing to do with kdbus in particular. It's an independent syscall that replaces many use cases for splice/vmsplice, even though it was introduced as part of the kdbus project - it's still a separate thing.
That was created for KDBUS but has more use than than being used for KDBUS exclusively. It still was written for KDBUS.
Re:“DBus is seriously screwed up”
by vezzy-fnord on Tuesday April 28, 2015 @11:05AM
(#9452863)
And so it was accepted and merged. That something good came out of kdbus is excellent, but that's no justification to merge in the whole package. A ton of proposed kernel additions end up like this - a few good ideas refined and accepted, and the rest thrown out.
Far from it. One of the core designs of kbus (which dbus cannot do because it's not in the kernel) is that you can seal the payload buffer from the sender so the receiver and use it safely concurrently without having to clone anything.
There is obviously a lot of general inefficiency in the userland libraries but not in the design of it.