James R. Leu wrote:
> I'm not asking for the impossible. Sequence numbers and/or client
> to server ACKs would solve the problem.
So what do you do when the client doesn't ACK and you run out of buffer
space ? Block all activities that may trigger netlink messages ?
Obviously, in this case (interface up/down transitions), netlink doesn't
scale well. A state-based interface would be better, e.g. netlink could
generate a bit vector indicating the states (or the transitions, if it
matters whether any have occurred), and update the vector until it has
been read by the client. The question is of course whether we really
need an optimized, scalable solution for this.
However, in general, I get the impression that netlink is vastly
over-engineered for most uses. Perhaps the situation could be improved
if distributions would start to include libnetlink (so you can expect
it to be available), and somebody would write a man page. Actually,
isn't netlink from BSD ? If they also have a libnetlink, maybe there's
some documentation too.
/ Werner Almesberger, ICA, EPFL, CH Werner.Almesberger@xxxxxxx /