search for: gartrell

Niklas - Thanks! Yeah, your Github issue was very useful for me to understand what is probably causing our issue (the syscall chain done on every UDP packet). Very interesting that you're able to see around 90% of a Gig line on bare metal. Were you ever able to make any further progress on adjusting Tinc based on the investigation in https://github.com/gsliepen/tinc/issues/110 ? Martin -

...ation that > DigitalOcean does is to add a feature to the Linux kernel to sending the > data for multiple UDP packets in one syscall, as mentioned in comment > https://github.com/gsliepen/tinc/issues/110#issuecomment-201949838. > > In the last message of that Kernel code review, Alex Gartrell says > "Sounds good to me. I'll get a patch turned around soon.". I don't know > if they ever got around to it. It might be worth shooting an email to ask! > It would be great to have that feature. > > For me personally the issue became less important, when I realis...

...on the type of virtualisation that DigitalOcean does is to add a feature to the Linux kernel to sending the data for multiple UDP packets in one syscall, as mentioned in comment https://github.com/gsliepen/tinc/issues/110#issuecomment-201949838. In the last message of that Kernel code review, Alex Gartrell says "Sounds good to me. I'll get a patch turned around soon.". I don't know if they ever got around to it. It might be worth shooting an email to ask! It would be great to have that feature. For me personally the issue became less important, when I realised that the syscall over...

Hello, Dave Taht, on Wed 02 Dec 2015 13:21:56 +0100, wrote: > I'd made a start on the send direction here: > https://github.com/dtaht/tinc/commits/master > > Perhaps that will help. Well, converting a sendto call into a sendmsg call is not really "hard" :) What will be really hard is getting multiple packet receive/send over the tap/tun device, because support for it