2015-07-31 2:12 GMT+08:00 Andy Lutomirski <l...@amacapital.net>: > > ISTM kdbus is trying to solve a few problems that really can't be > solved together: it wants (mostly) reliable delivery, it wants > globally ordered messages, and it wants broadcasts. That means that, > if message N gets broadcast, then, until *every* recipient has > received message N, message N and all of its successors need to be > buffered somewhere. I see how this works (by massive use of tmpfs), > but I don't see how it's going to work *well*.
For broadcast, what will the kernel behave if: 1. Lots of processes open netlink socket (to receive uevents), but not consume it. And someone continues to trigger uevents. 2. Lots of processes open inotify to monitor a directory, but not consume the events. And someone continues to operate files under the directory. ... I guess it may have to drop some data if the producer produces too fast(or the consumers consume too slow). What it needs may be a chance for recipients to know some broadcast data lost. -- Regards, - cee1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
