From: Rick Jones <rick.jones2@hp.com>
To: Cong Wang <amwang@redhat.com>
Cc: Pravin B Shelar <pshelar@nicira.com>, netdev <netdev@vger.kernel.org>
Subject: Re: A performance regression of gretap
Date: Wed, 10 Jul 2013 08:18:37 -0700 [thread overview]
Message-ID: <51DD7B4D.3060509@hp.com> (raw)
In-Reply-To: <327738182.1491147.1373450503005.JavaMail.root@redhat.com>
On 07/10/2013 03:01 AM, Cong Wang wrote:
> Hi, Pravin
>
> I just noticed the performance over gretap is very bad,
> which is probably caused by your GRE refactor patches.
>
> See below:
>
> # netperf -4 -H 192.168.2.1
> MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.2.1 () port 0 AF_INET
> Recv Send Send
> Socket Socket Message Elapsed
> Size Size Size Time Throughput
> bytes bytes bytes secs. 10^6bits/sec
>
> 87380 16384 16384 14.01 0.02
>
> Could you please take a look? And, gre tunnel is fine, this
> problem only exists for gretap. I reviewed the gretap code,
> but can't find any bug.
>
> It is very easy to reproduce, just setup a gretap device
> on both ends, and run netperf over it.
One way to provide more information from the netperf level in future
endeavours would be to extend the command line a bit:
netperf -4 -H 192.168.2.1 -c -C -- -o
throughput,local_sd,remote_ds,local_transport_retrans
and then again sans gretap. The -c/-C and [local|remote]_sd would be to
show the difference in path length, local_transport_retrans to see what
sort of difference there is in retransmissions.
happy benchmarking,
rick jones
next prev parent reply other threads:[~2013-07-10 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1025834928.1488534.1373450176613.JavaMail.root@redhat.com>
2013-07-10 10:01 ` A performance regression of gretap Cong Wang
2013-07-10 15:18 ` Rick Jones [this message]
2013-07-11 2:15 ` Cong Wang
2013-07-11 2:28 ` Pravin Shelar
2013-07-11 2:31 ` Cong Wang
2013-07-11 7:47 ` Pravin Shelar
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=51DD7B4D.3060509@hp.com \
--to=rick.jones2@hp.com \
--cc=amwang@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
/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).