Re: Poor network performance x86_64.. also with 3.13
On Sun, Feb 09, 2014 at 10:14:34AM -0800, Eric Dumazet wrote: > tcp_rmem[2] = 16777 > > Come on, the 640KB barrier was broken a long time ago ;) > > Feel free to investigate, I wont ;) Me too - it's not like I don't have anything else to do. :-) I was just wondering why 3.10 was fine even with these settings and 3.12 wasn't. Here's the original report: "I recently upgraded the Kernel from version 3.10 to latest stable 3.12.8, did the usual "make oldconfig" (resulting config attached). But now I noticed some _really_ low network performance." Link: http://lkml.kernel.org/r/52dad66f.7080...@dragonslave.de -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Poor network performance x86_64.. also with 3.13
On Sun, 2014-02-09 at 16:31 +0100, Borislav Petkov wrote: > On Sun, Feb 09, 2014 at 04:05:11PM +0100, Daniel Exner wrote: > > > cat /etc/sysctl.d/net.conf > > > net.ipv4.tcp_window_scaling = 1 > > > net.core.rmem_max = 16777216 > > > net.ipv4.tcp_rmem = 4096 87380 16777 > > > net.ipv4.tcp_wmem = 4096 1638 > > > > After removing those values I finally had sane iperf values. > > No idea how those got there, perhaps they made sense when I first setup > > the box, which is some years ago.. > > The only question that is left to clarify now is why do those values > have effect on 3.12.x and not on 3.10... tcp_rmem[2] = 16777 Come on, the 640KB barrier was broken a long time ago ;) Feel free to investigate, I wont ;) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Poor network performance x86_64.. also with 3.13
On Sun, Feb 09, 2014 at 04:05:11PM +0100, Daniel Exner wrote: > > cat /etc/sysctl.d/net.conf > > net.ipv4.tcp_window_scaling = 1 > > net.core.rmem_max = 16777216 > > net.ipv4.tcp_rmem = 4096 87380 16777 > > net.ipv4.tcp_wmem = 4096 1638 > > After removing those values I finally had sane iperf values. > No idea how those got there, perhaps they made sense when I first setup > the box, which is some years ago.. The only question that is left to clarify now is why do those values have effect on 3.12.x and not on 3.10... -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Poor network performance x86_64.. also with 3.13
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi all, Am Mon, 20 Jan 2014 23:37:52 +0100 schrieb Borislav Petkov : > On Mon, Jan 20, 2014 at 11:27:25PM +0100, Daniel Exner wrote: > > I just did the same procedure with Kernel Version 3.13: same poor > > rates. > > > > I think I will try to see of 3.12.6 was still ok and bisect from > > there. > > Or try something more coarse-grained like 3.11 first, then 3.12 and > then the -rcs in between. > I must apologize for suspecting the kernel for my problems. After some bisect attempts I finaly noticed the following: > cat /etc/sysctl.d/net.conf > net.ipv4.tcp_window_scaling = 1 > net.core.rmem_max = 16777216 > net.ipv4.tcp_rmem = 4096 87380 16777 > net.ipv4.tcp_wmem = 4096 1638 After removing those values I finally had sane iperf values. No idea how those got there, perhaps they made sense when I first setup the box, which is some years ago.. Anyway, thanks all for your help :) Greetings Daniel Exner -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAEBCgAGBQJS95knAAoJEPI6v6bI/QkfZYYP/37WBvygR7gLKqFTYfQA2ALE n6cOLrogoJT8Cf3q1fLqKiSzPToxSuPBTTmQtaNnhxLKTCPFHxLYPbTdtlXGTPB1 vFVJmXg8WAM/kQD/IoHrMsZsHfRWZE+RtQrUfeQ4Ava6abmniBufVe7ERMuF6ddW 02F5COtw74LJuSbxS70Cn3reog/ExoIYOYKQn6+FpoKTME4WnZtA8DJxo1r077RL mNqo3D4OMrYdPhxyRjLygtCnmXuX/yynV2czBnFkME4f1B4P/1hIzqYCxa2dBQIM Pfr+b/TtyVZA3DsE1d22f/+34EFWE/06EM5l8KwImmRHGA9Ffx77jKX4sAxN0Hhg 9ZJleeddk4NahXur5WNAV4lrkiLUgGauC0k721KwBFecFy2gYK/OUIyOm/oA3IPT WAEeGT4nCfCa1vYfoZVBn5UWOZo1eLm5qh6dmGb9FHukmwWTEplRRvYDPyJNfmRg 0j5mvn7ymFIbnmkVSnBFdfJH0I6XhhiHQ9H3cb9It9OLH5eEK1x4AW1okkAwrquQ oNYkpq54aJS/3oDokyWN/Gkvkmmk+4Q6tpxQge0AQPhrNeft5X7b8VhffstWhTSF kO1ULQ+zOtRUHF6T5523qVcS3pzFfqQKPYPhhQspGvuPJEr0M94i2JS016Z84Cz6 krmaHvSO/MKFkm7w+x5d =90En -END PGP SIGNATURE-
Re: Poor network performance x86_64.. also with 3.13
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi all, Am Mon, 20 Jan 2014 23:37:52 +0100 schrieb Borislav Petkov b...@alien8.de: On Mon, Jan 20, 2014 at 11:27:25PM +0100, Daniel Exner wrote: I just did the same procedure with Kernel Version 3.13: same poor rates. I think I will try to see of 3.12.6 was still ok and bisect from there. Or try something more coarse-grained like 3.11 first, then 3.12 and then the -rcs in between. I must apologize for suspecting the kernel for my problems. After some bisect attempts I finaly noticed the following: cat /etc/sysctl.d/net.conf net.ipv4.tcp_window_scaling = 1 net.core.rmem_max = 16777216 net.ipv4.tcp_rmem = 4096 87380 16777 net.ipv4.tcp_wmem = 4096 1638 After removing those values I finally had sane iperf values. No idea how those got there, perhaps they made sense when I first setup the box, which is some years ago.. Anyway, thanks all for your help :) Greetings Daniel Exner -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAEBCgAGBQJS95knAAoJEPI6v6bI/QkfZYYP/37WBvygR7gLKqFTYfQA2ALE n6cOLrogoJT8Cf3q1fLqKiSzPToxSuPBTTmQtaNnhxLKTCPFHxLYPbTdtlXGTPB1 vFVJmXg8WAM/kQD/IoHrMsZsHfRWZE+RtQrUfeQ4Ava6abmniBufVe7ERMuF6ddW 02F5COtw74LJuSbxS70Cn3reog/ExoIYOYKQn6+FpoKTME4WnZtA8DJxo1r077RL mNqo3D4OMrYdPhxyRjLygtCnmXuX/yynV2czBnFkME4f1B4P/1hIzqYCxa2dBQIM Pfr+b/TtyVZA3DsE1d22f/+34EFWE/06EM5l8KwImmRHGA9Ffx77jKX4sAxN0Hhg 9ZJleeddk4NahXur5WNAV4lrkiLUgGauC0k721KwBFecFy2gYK/OUIyOm/oA3IPT WAEeGT4nCfCa1vYfoZVBn5UWOZo1eLm5qh6dmGb9FHukmwWTEplRRvYDPyJNfmRg 0j5mvn7ymFIbnmkVSnBFdfJH0I6XhhiHQ9H3cb9It9OLH5eEK1x4AW1okkAwrquQ oNYkpq54aJS/3oDokyWN/Gkvkmmk+4Q6tpxQge0AQPhrNeft5X7b8VhffstWhTSF kO1ULQ+zOtRUHF6T5523qVcS3pzFfqQKPYPhhQspGvuPJEr0M94i2JS016Z84Cz6 krmaHvSO/MKFkm7w+x5d =90En -END PGP SIGNATURE-
Re: Poor network performance x86_64.. also with 3.13
On Sun, Feb 09, 2014 at 04:05:11PM +0100, Daniel Exner wrote: cat /etc/sysctl.d/net.conf net.ipv4.tcp_window_scaling = 1 net.core.rmem_max = 16777216 net.ipv4.tcp_rmem = 4096 87380 16777 net.ipv4.tcp_wmem = 4096 1638 After removing those values I finally had sane iperf values. No idea how those got there, perhaps they made sense when I first setup the box, which is some years ago.. The only question that is left to clarify now is why do those values have effect on 3.12.x and not on 3.10... -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Poor network performance x86_64.. also with 3.13
On Sun, 2014-02-09 at 16:31 +0100, Borislav Petkov wrote: On Sun, Feb 09, 2014 at 04:05:11PM +0100, Daniel Exner wrote: cat /etc/sysctl.d/net.conf net.ipv4.tcp_window_scaling = 1 net.core.rmem_max = 16777216 net.ipv4.tcp_rmem = 4096 87380 16777 net.ipv4.tcp_wmem = 4096 1638 After removing those values I finally had sane iperf values. No idea how those got there, perhaps they made sense when I first setup the box, which is some years ago.. The only question that is left to clarify now is why do those values have effect on 3.12.x and not on 3.10... tcp_rmem[2] = 16777 Come on, the 640KB barrier was broken a long time ago ;) Feel free to investigate, I wont ;) -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Poor network performance x86_64.. also with 3.13
On Sun, Feb 09, 2014 at 10:14:34AM -0800, Eric Dumazet wrote: tcp_rmem[2] = 16777 Come on, the 640KB barrier was broken a long time ago ;) Feel free to investigate, I wont ;) Me too - it's not like I don't have anything else to do. :-) I was just wondering why 3.10 was fine even with these settings and 3.12 wasn't. Here's the original report: I recently upgraded the Kernel from version 3.10 to latest stable 3.12.8, did the usual make oldconfig (resulting config attached). But now I noticed some _really_ low network performance. Link: http://lkml.kernel.org/r/52dad66f.7080...@dragonslave.de -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Poor network performance x86_64.. also with 3.13
On 01/20/2014 11:37 PM, Borislav Petkov wrote: On Mon, Jan 20, 2014 at 11:27:25PM +0100, Daniel Exner wrote: I just did the same procedure with Kernel Version 3.13: same poor rates. I think I will try to see of 3.12.6 was still ok and bisect from there. Or try something more coarse-grained like 3.11 first, then 3.12 and then the -rcs in between. Hm, on my machine 3.13 (latest git) has double throughtput of 3.11 (distro compiled) on loopback interface. 68Gb vs 33Gb (iperf). -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Poor network performance x86_64.. also with 3.13
On Mon, Jan 20, 2014 at 11:27:25PM +0100, Daniel Exner wrote: > I just did the same procedure with Kernel Version 3.13: same poor rates. > > I think I will try to see of 3.12.6 was still ok and bisect from there. Or try something more coarse-grained like 3.11 first, then 3.12 and then the -rcs in between. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Poor network performance x86_64.. also with 3.13
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am 18.01.2014 23:46, schrieb Daniel Exner: > Hi again, > > Am 18.01.2014 20:50, schrieb Borislav Petkov: >> + netdev. > Thx > > Am 18.01.2014 20:49, schrieb Holger Hoffstätte:> [This mail was > also posted to gmane.linux.kernel.] > >> On Sat, 18 Jan 2014 20:30:55 +0100, Daniel Exner wrote: > >>> I recently upgraded the Kernel from version 3.10 to latest >>> stable 3.12.8, did the usual "make oldconfig" (resulting >>> config attached). >>> >>> But now I noticed some _really_ low network performance. > >> Try: sysctl net.ipv4.tcp_limit_output_bytes=262144 > > Tried that. Even 10 times the value. Same effect. I just did the same procedure with Kernel Version 3.13: same poor rates. I think I will try to see of 3.12.6 was still ok and bisect from there. Greetings Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCgAGBQJS3aLFAAoJEPI6v6bI/Qkf9+4QAJkfljUsRQn6DA6gWy3XYsn4 ZB3F2Mu8kLsCMVjpASsi7+km2qTiFv4qGOgezHCJmqMcdCFszBweGQrnYBLA5PCD XSZ7G4S0U71aHWtY6iQd1q4ywnA21pfnGRqIpc5+OuIiIOm+YY+RXpJAHC5y1OVo MxsPL1ZVp/enJoZuvblw6i+JT+soAbSypPWcNQ78qb+CYzLVMLZHcqQvMwpAsRvQ LNKx8nyj8p32CdZo1GoT3f/nWvBeh/V/ViLrtt64u/oXMJyk5INVRFpSNUUviP8c 42y+r2K31+nY11K2dHsdJYbv5lZ8p8g0SNoLG1SrjgDspaptnT8jptxxn7GcQqdL PZ3waUB7qYU15IxCA2iXwNPqjtsv8V5l55H/cunKQgxNbb318ui/a3cW7+R++CeL onv9HFNUkHJiP/MvZJ1/FXE0AsjX70un9NuQ0+xFjCRwJ/YLZzCHkWMERcev500O vS1yFTGiVY1HndoA4VFYzEkjOyHgDHHQA+0JkfBspVlhL7ow9hccmULZtEn9LzwU 9rooQHyXwdKr6KIbsjHECyjIsBhW4Jfj6195bZ9ddBDBXSqYyGqjiuy7l7TjlZVa YmPNTlkEfMeXkO2h3km8TD2f+MPntYXkYjZVVUcK8NucgnIdLuWDk/GLrt73VTd8 Cww6B/u4YnGJSF5v/nit =xCa3 -END PGP SIGNATURE- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Poor network performance x86_64.. also with 3.13
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am 18.01.2014 23:46, schrieb Daniel Exner: Hi again, Am 18.01.2014 20:50, schrieb Borislav Petkov: + netdev. Thx Am 18.01.2014 20:49, schrieb Holger Hoffstätte: [This mail was also posted to gmane.linux.kernel.] On Sat, 18 Jan 2014 20:30:55 +0100, Daniel Exner wrote: I recently upgraded the Kernel from version 3.10 to latest stable 3.12.8, did the usual make oldconfig (resulting config attached). But now I noticed some _really_ low network performance. Try: sysctl net.ipv4.tcp_limit_output_bytes=262144 Tried that. Even 10 times the value. Same effect. I just did the same procedure with Kernel Version 3.13: same poor rates. I think I will try to see of 3.12.6 was still ok and bisect from there. Greetings Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCgAGBQJS3aLFAAoJEPI6v6bI/Qkf9+4QAJkfljUsRQn6DA6gWy3XYsn4 ZB3F2Mu8kLsCMVjpASsi7+km2qTiFv4qGOgezHCJmqMcdCFszBweGQrnYBLA5PCD XSZ7G4S0U71aHWtY6iQd1q4ywnA21pfnGRqIpc5+OuIiIOm+YY+RXpJAHC5y1OVo MxsPL1ZVp/enJoZuvblw6i+JT+soAbSypPWcNQ78qb+CYzLVMLZHcqQvMwpAsRvQ LNKx8nyj8p32CdZo1GoT3f/nWvBeh/V/ViLrtt64u/oXMJyk5INVRFpSNUUviP8c 42y+r2K31+nY11K2dHsdJYbv5lZ8p8g0SNoLG1SrjgDspaptnT8jptxxn7GcQqdL PZ3waUB7qYU15IxCA2iXwNPqjtsv8V5l55H/cunKQgxNbb318ui/a3cW7+R++CeL onv9HFNUkHJiP/MvZJ1/FXE0AsjX70un9NuQ0+xFjCRwJ/YLZzCHkWMERcev500O vS1yFTGiVY1HndoA4VFYzEkjOyHgDHHQA+0JkfBspVlhL7ow9hccmULZtEn9LzwU 9rooQHyXwdKr6KIbsjHECyjIsBhW4Jfj6195bZ9ddBDBXSqYyGqjiuy7l7TjlZVa YmPNTlkEfMeXkO2h3km8TD2f+MPntYXkYjZVVUcK8NucgnIdLuWDk/GLrt73VTd8 Cww6B/u4YnGJSF5v/nit =xCa3 -END PGP SIGNATURE- -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Poor network performance x86_64.. also with 3.13
On Mon, Jan 20, 2014 at 11:27:25PM +0100, Daniel Exner wrote: I just did the same procedure with Kernel Version 3.13: same poor rates. I think I will try to see of 3.12.6 was still ok and bisect from there. Or try something more coarse-grained like 3.11 first, then 3.12 and then the -rcs in between. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Poor network performance x86_64.. also with 3.13
On 01/20/2014 11:37 PM, Borislav Petkov wrote: On Mon, Jan 20, 2014 at 11:27:25PM +0100, Daniel Exner wrote: I just did the same procedure with Kernel Version 3.13: same poor rates. I think I will try to see of 3.12.6 was still ok and bisect from there. Or try something more coarse-grained like 3.11 first, then 3.12 and then the -rcs in between. Hm, on my machine 3.13 (latest git) has double throughtput of 3.11 (distro compiled) on loopback interface. 68Gb vs 33Gb (iperf). -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
