mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@redhat.com>, linux-net@vger.kernel.org
Subject: Re: [BETA-0.94] Fifth test release of Tigon3 driver
Date: Mon, 04 Mar 2002 10:56:42 -0500	[thread overview]
Message-ID: <3C83993A.94FE655E@mandrakesoft.com> (raw)
In-Reply-To: <20020304.041252.13772021.davem@redhat.com> <20020304164453.A27587@stud.ntnu.no>

Thomas Langås wrote:
> 
> David S. Miller:
> > How does this thing perform for people?  In particular lmbench
> > 'bw_tcp' and 'lat_tcp' numbers over gigabit on beefy hardware are
> > considered very interesting...
> 
> Ok, here I am again; doing some benchmarking :)
> 
> (all this is done with same hardware as before, and your tg3 v0.94 driver in
> both ends):
> test8:/usr/src/LMbench/bin/i686-pc-linux-gnu# ./bw_tcp 129.241.56.160
> initial bandwidth measurement: move=10485760, usecs=117352: 89.35 MB/sec
> move=693633024, XFERSIZE=65536
> Socket bandwidth using 129.241.56.160: 104.73 MB/sec
> 
> test8:/usr/src/LMbench/bin/i686-pc-linux-gnu# ./lat_tcp 129.241.56.160
> TCP latency using 129.241.56.160: 100.0089 microseconds
> 
> Do you want any more benchmark; just say so :)

I am always interested in more benchmarks, never ask this question :):)

A comparison between bcm5700 and tg3 would be interesting, for each new
release, if you were willing to do that.

And, what MTU are you using?  You may have answered this earlier and I
forgot :)  If you -are- on a gigabit network, then you [currently] must
manually enable an MTU of 9000 (jumbo frames).

	Jeff



-- 
Jeff Garzik      |
Building 1024    |
MandrakeSoft     | Choose life.

  reply	other threads:[~2002-03-04 15:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-04 12:12 David S. Miller
2002-03-04 15:44 ` Thomas Langås
2002-03-04 15:56   ` Jeff Garzik [this message]
2002-03-04 16:00     ` Thomas Langås
2002-03-04 16:03       ` Jeff Garzik
2002-03-04 16:26     ` Thomas Langås
2002-03-05  7:45     ` David S. Miller
2002-03-04 16:29   ` Steffen Persvold

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=3C83993A.94FE655E@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@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

all inboxes | Powered by JetHome®