There are many way of being unreliable. If it means "bad things
happen and nobody is told about it", then yes, this would be
strange in this context. Howver, "loss due to congestion" is a
perfectly reasonable behaviour (*), and netlink indicates when
this has occurred.
If you get more events than you can queue or compress (e.g. if
you have on/off events but are only interested in the current
status, you could aggregate any number of such events in just
one bit), congestion is possible.
> Having to manage acks on that kind of communication is both
> painful and quasi-untestable.
<ObPlug>
Ha ! That's exactly the kind of stuff I'm writing umlsim for :-)
http://umlsim.sourceforge.net/
</ObPlug>
- Werner
-- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net / /_http://www.almesberger.net/____________________________________________/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/