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 11:06:41 +0200 [thread overview]
Message-ID: <4FE192A1.6000000@profihost.ag> (raw)
In-Reply-To: <1340181676.4604.838.camel@edumazet-glaptop>
Am 20.06.2012 10:41, schrieb Eric Dumazet:
> On Wed, 2012-06-20 at 10:21 +0200, Stefan Priebe - Profihost AG wrote:
>> Am 20.06.2012 09:22, schrieb Eric Dumazet:
> Yes, you already told that in subject line.
>
> single tcp flow ?
I use iperf - i think it uses just a single tcp flow. But i'm not sure.
> You seem to have a switch or something that drops packets in this case.
> You could try to rate limit to 9Gb/s and see if it is better.
Sadly i can't rate limit to 9Gbit/s on the switch.
> Here, I roughly have same bandwidth with tcp_timestamps on or off, with
> ixgbe cards and net-next kernels.
Mhm strange. Do you have any vague idea what could cause this? Any wrong
reordering of the packets without tcp_timestamps?
Stefan
next prev parent reply other threads:[~2012-06-20 9:06 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
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 [this message]
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=4FE192A1.6000000@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.