On Wed, Sep 20, 2006 at 09:28:51AM +1200, Ian McDonald wrote: > Understand totally. I wasn't saying tx queueing would solve world > hunger. It just helps you with the proper approach - doesn't solve it I'm sure DCCP will one day solve world hunger---TCP failed. > If tx queueing doesn't help, how do you drain your tx queue when you > don't have one :-) I said that on purpose to make you "happy" =D but I didn't add a reference---you spotted it anyway. One thing I want to experiment with [now that we have tx queueing] is a "writev" style API for sending multiple packets with one syscall. Not quite writev because that is scatter gather i/o but i call it writev anyway =D. Perhaps we can add a flag to sendmsg() which tells it to use the iov as multiple packets rather than a single packet scattered about. The idea is that you should be able to send across bulk data with less context switches. The combination of writev, tx queueing and ccid pull should lower CPU utilization, and I'm wondering by how much [i.e. is it worth the effort?] - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
