On 08/06/2015 05:21 PM, Andy Lutomirski wrote: > Maybe gdbus really does use kdbus already, but on > very brief inspection it looked like it didn't at least on my test VM.
No, it's not in any released version yet. The patches for that are being worked on though and look promising. > If the client buffers on !EPOLLOUT and has a monster buffer, then > that's the client's problem. > > If every single program has a monster buffer, then it's everyone's > problem, and the size of the problem gets multiplied by the number of > programs. The size of the memory pool of a bus client is chosen by the client itself individually during the HELLO call. It's pretty much the same as if the client allocated the buffer itself, except that the kernel does it on their behalf. Also note that kdbus features a peer-to-peer based quota accounting logic, so a single bus connection can not DOS another one by filling its buffer. Thanks, Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
