netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Leininger <mlleinin@hpcn.ca.sandia.gov>
To: Roland Dreier <rolandd@cisco.com>
Cc: netdev@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
	openib-general@openib.org
Subject: Re: Timeline of IPoIB performance
Date: Wed, 12 Oct 2005 11:28:26 -0700	[thread overview]
Message-ID: <1129141706.13945.509.camel@localhost> (raw)
In-Reply-To: <52mzle7k2i.fsf@cisco.com>

On Wed, 2005-10-12 at 09:53 -0700, Roland Dreier wrote:
>     Herbert> Try reverting the changeset
> 
>     Herbert> 314324121f9b94b2ca657a494cf2b9cb0e4a28cc
> 
>     Herbert> which lies between these two points and may be relevant.
> 
> Matt, I pulled this out of git for you.  I guess Herbert is suggesting
> to patch -R the below against 2.6.12-rc5:

I applied your patch suggest by Herbert:

http://www.mail-archive.com/openib-general%40openib.org/msg11415.html

to my 2.6.12-rc5 tree and IPoIB performance improved back to the ~475
MB/s range for my EM64T system.  The data is below.

I'm building/testing 2.6.14-rc4 with and without this patch now.


All benchmarks are with RHEL4 x86_64 with HCA FW v4.7.0
dual EM64T 3.2 GHz PCIe IB HCA (memfull)

Kernel           OpenIB    msi_x  netperf (MB/s)  
2.6.14-rc3      in-kernel    1     374 
2.6.13.2        svn3627      1     386 
2.6.13.2        in-kernel    1     394 
2.6.12.5-lustre in-kernel    1     399  
2.6.12.5        in-kernel    1     402 
2.6.12          in-kernel    1     406 
2.6.12-rc6      in-kernel    1     407
2.6.12-rc5      in-kernel    1     405                        <<<<
2.6.12-rc5                                                    <<<<
 - remove changeset 314324121f9b94b2ca657a494cf2b9cb0e4a28cc  <<<<
                in-kernel    1     474                        <<<<
2.6.12-rc4      in-kernel    1     470 
2.6.12-rc3      in-kernel    1     466 
2.6.12-rc2      in-kernel    1     469 
2.6.12-rc1      in-kernel    1     466
2.6.11          in-kernel    1     464 
2.6.11          svn3687      1     464 
2.6.9-11.ELsmp  svn3513      1     425  (Woody's results, 3.6Ghz EM64T) 

  - Matt

  reply	other threads:[~2005-10-12 18:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1EPIxF-0001Cp-00@gondolin.me.apana.org.au>
2005-10-12 16:53 ` Timeline of IPoIB performance Roland Dreier
2005-10-12 18:28   ` Matt Leininger [this message]
2005-10-13  1:24     ` Matt Leininger
2005-10-13  1:48       ` Herbert Xu
     [not found] <1128672413.13948.326.camel@localhost>
     [not found] ` <52br20lsei.fsf@cisco.com>
2005-10-08  2:25   ` 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

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=1129141706.13945.509.camel@localhost \
    --to=mlleinin@hpcn.ca.sandia.gov \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=rolandd@cisco.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).