Yes, but using such a high value makes latency go into the
For low packet rates.
I'd much rather see dynamic settings based upon packet rate.
It's easy to resurrect the ancient code from the early
tg3 days which does this.
If that is the stuff I think it was, it was giving me _fits_ trying to run
TCP_RR tests. Results bounced all over the place. I think it was trying to
kick-in at pps rates that were below the limits of what a pair of systems could
do on a single, synchronous request/response stream.
Now, modulo an OS that I cannot mention because its EULA forbits discussing
results with third parties, where the netperf TCP_RR perf is 8000 transactions
per second no matter how powerful the CPU... if folks are simply free to set
high coalescing parms on their own, presumably with some knowledge of their
workloads, wouldn't that be enough? That has been "good enough" for one OS I
can discuss - HP-UX - and its bcm570X-based GbE NICs and before to Tigon2.