Re:Bus1: a new Linux interprocess communication proposal
by saynsedit on Thursday August 18, 2016 @08:51AM
(#12312079)
There's no case for this usually marginal speed benefit.
Most programs are dealing with vastly slower bottlenecks. Like network or disk latency. IPC latency is so far down the list of priorities in terms of things to optimize.
Not to mention that regular user-kernel-user buffer copying is plenty fast now, especially since the buffers will likely be cache-resident. Zero-copy is mostly hype without performance numbers to back it up. Don't need this complex message sealing mechanism.
Re:Bus1: a new Linux interprocess communication proposal
by dooglius on Thursday August 18, 2016 @10:46AM
(#12312862)
I don't see anything described that can't be done in a userspace library through shared memory. Maybe security is a concern, where we don't trust some nodes that might be exploited not to be able to screw with the shared memory? But then zero-copy would be off the table for the same reasons, no?
Re:Bus1: a new Linux interprocess communication proposal
by qwertyuiop924 on Thursday August 18, 2016 @07:49AM
(#12311717)
Yeah, but is it worth the cost? I would say no.
The last is something you need kernel help to enforce.