> With simply removing the notify here, it does help the case when TX > overrun hits too often, for example for 1K message size, the single > TCP_STREAM performance improved from 2.xGb/s to 4.xGb/s.
OK, we'll be getting rid of the "kick on full", so please delete that on all benchmarks. Now, does the capacity check before add_buf() still win anything? I can't see how unless we have some weird bug. Once we've sorted that out, we should look at the more radical change of publishing last_used and using that to intuit whether interrupts should be sent. If we're not careful with ordering and barriers that could introduce more bugs. Anything else on the optimization agenda I've missed? Thanks, Rusty. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
