On 10/27/2010 07:09 PM, Bill Gatliff wrote: > On a buffer overflow, the head and tail pointers collide. > This makes the buffer suddenly look empty, rather than > full, which may confuse applications. This is actually an important regulatory effect which increases the ability for the client to catch up. > This patch moves the tail pointer up one event on a buffer > overflow, which "consumes" the oldest event in the buffer > to make room for the incoming event. Thus, although data > is lost due to the overflow (which is unavoidable), the > data that remains is both recent and still time-ordered. As Dmitry said, snapping discards to the event synchronization boundaries could be useful, but I doubt it is really worthwhile. Henrik -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
