From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: 10GBE performance drop with net.ipv4.tcp_timestamps=0
Date: Wed, 20 Jun 2012 09:00:50 +0200 [thread overview]
Message-ID: <4FE17522.5050005@profihost.ag> (raw)
In-Reply-To: <1340141493.4604.773.camel@edumazet-glaptop>
Am 19.06.2012 23:31, schrieb Eric Dumazet:
> On Tue, 2012-06-19 at 23:08 +0200, Stefan Priebe wrote:
>> i'm testing 10GBE speed with tweo servers. One with 3.5-rc3 nd thoe
>> other one whith RHEL 6 (2.6.32 kernel).
>>
>> I noticed that setting
>> net.ipv4.tcp_timestamps=0
>>
>> descreased the performance from 9,7 Full Duplex to 3-4Gb/s.
>>
>> Is this bahviour fine? What should / could i tet?
>>
>
> Really, you should provide more input than that, if you really want us
> to help.
*arg* forgot to add the pastebin links. Sorry. Speed degraded in this
case from 9,88Gbit/s to 2,45Gbit/s. When i turn on timestamps it's
perfect again. Server A has 3.5.0-rc3 and server B has an RHEL6 2.6.32
kernel.
Before:
http://pastebin.com/raw.php?i=1gVraWVc
After:
http://pastebin.com/raw.php?i=NSh8Y29s
Thanks,
Stefan
next prev parent reply other threads:[~2012-06-20 7:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 21:08 10GBE performance drop with net.ipv4.tcp_timestamps=0 Stefan Priebe
2012-06-19 21:31 ` Eric Dumazet
2012-06-20 7:00 ` Stefan Priebe - Profihost AG [this message]
2012-06-20 7:22 ` Eric Dumazet
2012-06-20 8:21 ` Stefan Priebe - Profihost AG
2012-06-20 8:41 ` Eric Dumazet
2012-06-20 9:06 ` Stefan Priebe - Profihost AG
2012-06-20 9:12 ` Stefan Priebe - Profihost AG
2012-06-20 9:17 ` Eric Dumazet
2012-06-20 9:25 ` Stefan Priebe - Profihost AG
2012-06-20 9:28 ` Eric Dumazet
2012-06-20 9:33 ` Stefan Priebe - Profihost AG
2012-06-20 9:47 ` Eric Dumazet
2012-06-20 9:50 ` Stefan Priebe - Profihost AG
2012-06-20 10:06 ` Eric Dumazet
2012-06-20 11:08 ` Eric Dumazet
2012-06-20 9:16 ` Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FE17522.5050005@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).