Only out of order data should be pruned so this is fine. We have a situation
where we are out of resources, we wish the other end to slow down and we need
to flag the situation but cannot shrink the window. Dropping a frame is
exactly that.
In fact I found it worked extremely well because it also tended to cause
silly window avoidance and get the other end back sending MTU sized blocks
as the stall gave the sender time to build full blocks of data.
The only really important thing for current code will be that rx_copybreak
is > about 2/3rds of the MTU of the device using it.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html