WireGuard: next generation in-kernel modern VPN

Re:WireGuard: next generation in-kernel modern VPN by tinco on Wednesday June 29, 2016 @05:08AM (#12000369)

Why necessarily lower speed? Are you hinting at bounds checking? I would think that a rust implementation might have slightly more pressure on the CPU but would not effectively be slower. Am I wrong?

[ Parent | on HN ]

Re:WireGuard: next generation in-kernel modern VPN by steveklabnik on Wednesday June 29, 2016 @06:21AM (#12000639)

I took it as "the Rust version is in userspace, and therefore will be slower than the in-kernel version."

[ Parent | on HN ]

Re:WireGuard: next generation in-kernel modern VPN by tinco on Wednesday June 29, 2016 @06:57AM (#12000761)

Right, I heard about the Rust kernel module[1], but perhaps its environment isn't friendly enough yet to attempt to port a project like this to?

edit: Just read a little bit of its source, apparently you have to disable std, and he replaces it with his own linux_std that at this point has only printf implemented. So yeah it'd be a pretty intense project if one would attempt it :)

1] https://github.com/tsgates/rust.ko

[ Parent | on HN ]

Re:WireGuard: next generation in-kernel modern VPN by steveklabnik on Wednesday June 29, 2016 @07:01AM (#12000781)

Elsewhere in the thread, they talk about upstreaming some code into the kernel itself; so it has to be in C for that. That's my guess, anyway.

(disabling std is standard in environments like this; and you still get libcore, which is a lot of stuff!)

[ Parent | on HN ]

Re:WireGuard: next generation in-kernel modern VPN by tinco on Wednesday June 29, 2016 @07:17AM (#12000839)

What are the odds of getting Linus to approve of Rust? It would be the greatest thing ever. Imagine the impact on the C++ community.. You might say I'm a dreamer, but I'm not the only one ;)

[ Parent | on HN ]

Re:WireGuard: next generation in-kernel modern VPN by steveklabnik on Wednesday June 29, 2016 @01:25PM (#12003118)

I would imagine very low.

[ Parent | on HN ]