splice() gets network receive

Jul 17, 2007 17:59

As a follow-up to my earlier excitement, more fun developments in splice() syscall land ( Read more... )

tech, linux, perlbal

Leave a comment

Comments 3

Biggest overhead? baudehlo July 18 2007, 02:54:09 UTC
Is copying network packets really the biggest overhead in perlbal? I would have thought more likely it's just perl data structures getting copied all the time.

Though I guess any small win is worth it with the amount of data you're copying around.

Reply

Re: Biggest overhead? brad July 18 2007, 03:06:10 UTC
I know where Perl uses CPU, so I'm pretty careful to avoid painful stuff. I believe the reads/writes syscalls were actually a big part of the last profile I did.

Reply


xb95 July 18 2007, 02:59:17 UTC
Good stuff. You've only been talking about wanting that for at least three years now (as long as I can remember).

How long before that hits mainstream (Debian/Ubuntu/RHEL/CentOS/FC/whatever) kernels that are part of main distributions?

Reply


Leave a comment

Up