From: Gagan Arneja <[EMAIL PROTECTED]> Date: Thu, 10 May 2007 12:43:53 -0700
> It's not just small packets. The cost of calling hard_start_xmit/byte > was rather high on your particular device. I've seen PCI read > transaction in hard_start_xmit taking ~10,000 cycles on one particular > device. Count the cycles your brand of NIC is taking in it's > xmit_routine. The worse it is, the stronger your case for cluster > transmits. > > Also, I think, you don't have to chain skbs, they're already chained in > Qdisc->q. All you have to do is take the whole q and try to shove it > at the device hoping for better results. But then, if you have rather > big backlog, you run the risk of reordering packets if you have to requeue. If the qdisc is packed with packets and we would just loop sending them to the device, yes it might make sense. But if that isn't the case, which frankly is the usual case, you add a non-trivial amount of latency by batching and that's bad exactly for the kind of applications that send small frames. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
