On Tue, 1 Jun 2010, Greg KH wrote: > On Tue, Jun 01, 2010 at 07:39:16PM -0400, Chris Frey wrote: > > On Tue, Jun 01, 2010 at 03:46:18PM -0700, Greg KH wrote: > > > usbmon is. > > > > > > Please read the documentation for how to use the binary interface in the > > > file at Documentation/usb/usbmon.txt > > > > Oops, thanks. I guess I was expecting that there would be tools already > > available for this, instead of cobbling together my own code. > > There are tools already around. Wireshark can handle usbmon traces, and > there's also a java application (or was it python) that could do it as > well in a very pretty format. Look in the linux-usb archives for > details. For a lower-level binary interface much like the text interface, see the "usbmon 6" link at <http://people.redhat.com/zaitcev/linux/>. > > Can I be sure that the usbmon binary buffers will not drop usb packets > > no matter how busy my system is? I don't want it to be like the dmesg > > buffer where usbfs_snoop output went. > > I think it will handle all of them but of course, nothing is ever > guaranteed :) You should check with Pete Zaitcev. I don't know whether or not the binary interface guarantees delivery of all packets -- if the user process stops reading then eventually the only choices are to drop packets or to run out of memory. However there is a statistics interface in usbmon which lists the number of packets that have been dropped, so at least you can tell if any were lost. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
