From: Roland Dreier <rolandd@cisco.com>
To: Matt Leininger <mlleinin@hpcn.ca.sandia.gov>
Cc: netdev@vger.kernel.org, openib-general@openib.org
Subject: Re: Timeline of IPoIB performance
Date: Mon, 10 Oct 2005 21:03:35 -0700 [thread overview]
Message-ID: <52u0fod7jc.fsf@cisco.com> (raw)
In-Reply-To: <527jcldj4n.fsf@cisco.com> (Roland Dreier's message of "Mon, 10 Oct 2005 16:53:12 -0700")
Roland> I might get a chance to do it tonight... I'll post if I do.
I'm giving it a shot but I just can't reproduce this well on my
systems. I do see a pretty big regression between 2.6.12-rc4 and
2.6.14-rc2, but 2.6.12-rc5 looks OK on my systems.
I reflashed to FW 4.7.0 (mem-ful) and built netperf 2.4.1.
With 2.6.12-rc4 I've seen runs as slow as:
TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.145.2 (192.168.145.2) port 0 AF_INET
Recv Send Send Utilization Service Demand
Socket Socket Message Elapsed Send Recv Send Recv
Size Size Size Time Throughput local remote local remote
bytes bytes bytes secs. MBytes /s % S % U us/KB us/KB
87380 16384 16384 10.00 553.71 37.46 -1.00 2.642 -1.000
and with 2.6.12-rc5 I've seen runs as fast as:
TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.145.2 (192.168.145.2) port 0 AF_INET
Recv Send Send Utilization Service Demand
Socket Socket Message Elapsed Send Recv Send Recv
Size Size Size Time Throughput local remote local remote
bytes bytes bytes secs. MBytes /s % S % U us/KB us/KB
87380 16384 16384 10.00 581.82 39.58 -1.00 2.657 -1.000
so not much difference there. With 2.6.14-rc2, the best of 10 runs was:
TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.145.2 (192.168.145.2) port 0 AF_INET
Recv Send Send Utilization Service Demand
Socket Socket Message Elapsed Send Recv Send Recv
Size Size Size Time Throughput local remote local remote
bytes bytes bytes secs. MBytes /s % S % U us/KB us/KB
87380 16384 16384 10.01 497.00 39.71 -1.00 3.121 -1.000
so we've definitely lost something there.
Time to do some more bisecting...
- R.
next prev parent reply other threads:[~2005-10-11 4:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1128672413.13948.326.camel@localhost>
[not found] ` <52br20lsei.fsf@cisco.com>
2005-10-08 2:25 ` Timeline of IPoIB performance Matt Leininger
2005-10-10 18:23 ` Roland Dreier
2005-10-10 20:03 ` Michael S. Tsirkin
2005-10-10 21:03 ` Roland Dreier
2005-10-10 20:17 ` Rick Jones
2005-10-10 20:58 ` Roland Dreier
2005-10-10 21:22 ` Rick Jones
2005-10-10 21:26 ` Grant Grundler
2005-10-10 23:30 ` Grant Grundler
2005-10-11 0:51 ` Andi Kleen
2005-10-10 23:25 ` Matt Leininger
2005-10-10 23:38 ` Roland Dreier
2005-10-10 23:44 ` Matt Leininger
2005-10-10 23:53 ` Roland Dreier
2005-10-11 4:03 ` Roland Dreier [this message]
[not found] <E1EPIxF-0001Cp-00@gondolin.me.apana.org.au>
2005-10-12 16:53 ` Roland Dreier
2005-10-12 18:28 ` Matt Leininger
2005-10-13 1:24 ` Matt Leininger
2005-10-13 1:48 ` Herbert Xu
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=52u0fod7jc.fsf@cisco.com \
--to=rolandd@cisco.com \
--cc=mlleinin@hpcn.ca.sandia.gov \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.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).