Yes, you can think of the lower bits the frame number and the upper bits the number of overflows.
There isn’t any reason to interpret it as anything other than a 64-bit integer nor to specify the division. —scott > On Jan 5, 2017, at 10:35 PM, Guy Harris <g...@alum.mit.edu> wrote: > > On Jan 5, 2017, at 10:11 PM, Scott Deandrea <sdeand...@apple.com> wrote: > >> An interrupt is generated when the frame number rolls over and we use this >> to increment the upper bits so the frame number can grow beyond 11 bits. >> This allows software consuming the frame number not to worry about the frame >> wrap when scheduling isochronous I/O. > > So the lower 11 bits are the frame number and the upper bits are, in effect, > a count of frame number overflows. > > Is there any reason to interpret it as anything other than a 64-bit integer, > or to specify that division in the spec for the format? _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
