On Wednesday 24 May 2006 22:08, Jeff Garzik wrote: > Brent Cook wrote: > > Note that this is just clearing the hardware statistics on the interface, > > and > > would not require any kind of atomic_increment addition for interfaces that > > support that. It would be kind-of awkward to implement this on drivers that > > > > increment stats in hardware though (lo, vlan, br, etc.) This also brings up > > the question of resetting the stats for 'netstat -s' > > If you don't atomically clear the statistics, then you are leaving open > a window where the stats could easily be corrupted, if the network > interface is under load.
It could be handled by RCU with some moderately complex code (clear and clear again after a RCU quiescent period) But the real problem is that the user will always miss events during the clear operation. That is why it is inherently racy. An atomic user visible get-and-clear wouldn't have this problem, but it would be probably nasty to implement lockless without risking livelock on a busy system. And I also doubt it would have a nice user interface in the file system. And really is it that hard to do a before-after diff? I don't think so. > > See... this opens doors to tons of complexity. Agreed. -Andi - 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
