On Thu, 2007-15-11 at 10:11 +0800, Herbert Xu wrote: > We don't make use of that on recvmsg() though although theoretically > user-space is supposed to be ready to handle that too.
iproute2 handles that well. Anyone writting netlink apps should program with the thought that a single received datagram will include many netlink messages. On the concept of putting some generation marker/counter: It is one of those things that have bothered me as well for sometime, but i cant think of a clean way to solve it for every user of netlink. One way to transport this from the kernel is stash it in the netlink sequence but that would violate things when a user expects a specific sequence. For the ifla/iflink, it should be trivial to solve by adding a marker in the kernel that gets set to jiffies (or some incremental counter) every time an event happens. You then transport this to user space as an attribute anytime someone does a GET. Clearly the best way to solve it is to be generic, but we would need to revamp netlink totaly. Note, we do today signal to user space that a "message was lost" because of buffer overrun. So a hack (not applicable to the poster given they dont have a daemon) would be to listen to events and set the rx socket buffer to be very small so you loose every message. cheers, jamal - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
