> This patch adds checking for how many bytes have been inserted into the tty > buffer and places data which hasn't been inserted into a pending buffer list. > The pending buffer list is pushed to the tty buffer when the tty unthrottles I don't think this is the way to tackle it. If the kernel tty buffer code is shedding data then not only have we asserted a throttle but 64K has been accumulated or the system is out of memory. So the questions to me are: a) Why is your setup filling 64K in the time it takes the throttle response to occur b) Do we care (is the right thing to do to lose bits anyway at that point) c) What should we do about it in the *general* case It seems to me either its a cdc-acm specific problem with throttle response behaviour, or its a general case at very high speed (which seems more likely). In neither case is adding an extra queue to paper over it the right solution. -- 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
