On 9/20/06, Andrea Bittau <a.bittau@xxxxxxxxxxxx> wrote:
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?]
I agree that APIs can improve and after I've done my current research I'm going to look at that some more. The sendmsg code can certainly be modified - I've done this for my bestpacketnext code. If you want have a look at it on my website - it is real ugly but it works. -- Ian McDonald Web: http://wand.net.nz/~iam4 Blog: http://imcdnzl.blogspot.com WAND Network Research Group Department of Computer Science University of Waikato New Zealand - 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
