Re: [Openvpn-devel] Linux tun/tap performance issues

2010-03-16 Thread Jan Just Keijser
Hi David, David Sommerseth wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/03/10 16:29, Jan Just Keijser wrote: More tests, this time with 'oprofile' : here's a recap: - nothing changed on the server side: openvpn --ifconfig 10.222.0.1 10.222.0.2 --dev tun --secret secret.key

Re: [Openvpn-devel] Linux tun/tap performance issues

2010-03-15 Thread David Sommerseth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/03/10 16:29, Jan Just Keijser wrote: > More tests, this time with 'oprofile' : here's a recap: > - nothing changed on the server side: > openvpn --ifconfig 10.222.0.1 10.222.0.2 --dev tun --secret secret.key > --cipher none > > - upgraded to

Re: [Openvpn-devel] Linux tun/tap performance issues

2010-03-15 Thread Jan Just Keijser
More tests, this time with 'oprofile' : here's a recap: - nothing changed on the server side: openvpn --ifconfig 10.222.0.1 10.222.0.2 --dev tun --secret secret.key --cipher none - upgraded to kernel 2.6.32.9-70.fc12.x86_64 on my laptop - selinux is disabled - installed the debuginfo rpms to

Re: [Openvpn-devel] Linux tun/tap performance issues

2010-03-11 Thread Jan Just Keijser
Hi all, just ran a very silly test, all with openvpn 2.1.1, on my laptop running FC12 (2.6.31.12-174.2.22.fc12.x86_64) , Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz, connected to a 100 Mbps LAN server side: openvpn --ifconfig 10.222.0.1 10.222.0.2 --dev tun --secret secret.key --cipher

Re: [Openvpn-devel] Linux tun/tap performance issues

2010-03-08 Thread Peter Stuge
James Yonan wrote: > all of the CPU-intensive cryptographic operations are being done in > user space. Could some kind of crypto acceleration of OpenSSL be in play? //Peter

[Openvpn-devel] Linux tun/tap performance issues

2010-03-08 Thread James Yonan
I believe this has been discussed before, but I noticed recently that a Linux-based OpenVPN client (Linux 2.6.24, OpenVPN 2.1.1) spends a lot more CPU time in kernel space than in user space. This is surprising, given the fact that all of the CPU-intensive cryptographic operations are being