On Fri, 2007-05-04 at 13:08 -0700, Pete Zaitcev wrote: > I still do not understand why it is important to limit the size > this way. I see that your patch is shorter than mine, which is good. > But it seems to create an excessively complicated bunch of unions. > I cannot comprehend the logic which drives this development and > it bothers me. I'll need to look at the libpcap, I suppose.
The usbmon header is provided 'as is' to the application layer via a specific libpcap data link type (to take advantage of the 'zero copy' memory mapped access). A change to the header size (or binary layout) will require a different data-link-type and will make new libpcap trace incompatible with old ones. My goal is to minimize the amount of rough edges on both kernel and user space side, and I thought that keeping the interface compatible was the right way to do that... Anyway I agree that the usbmon header used in my patch is (more than) a bit complicated. Obviously fell free to not use this implementation. ciao, Paolo -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Vuoi essere in grado di saper scrivere un Business Plan vincente? Impara subito seguendo questo videocorso multimediale Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=6198&d=4-5 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
