All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Chan" <mchan@broadcom.com>
To: "Ben Greear" <greearb@candelatech.com>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: BCM5704 performance questions.
Date: Thu, 09 Jun 2005 16:56:16 -0700	[thread overview]
Message-ID: <1118361376.5838.20.camel@rh4> (raw)
In-Reply-To: <42A8E0FE.3020708@candelatech.com>

On Thu, 2005-06-09 at 17:38 -0700, Ben Greear wrote:

> 
> *  Is the BCM5704 chipset/driver really that much slower?
> 

Unfortunately, the 5704 requires the "ONE_DMA" workaround which will
limit throughput in a PCIX 100/133 bus. If you comment out the line that
sets the DMA_RWCTRL_ONE_DMA flag in tg3.c, you should see improved
performance. However, you may run into some DMA issues on certain
systems.

> *  Is there some information on tuning the tg3 somewhere?
>     (I didn't see a Documentation/networking/tg3.txt file, for instance)
> 
> *  Is there a way to verify the bus speed that the NIC is running at?
>     (ethtool -d ethX gives lots of meaningless (to me) hex)
> 

tg3 probing string for each device will tell you the bus type, width,
and speed.

  reply	other threads:[~2005-06-09 23:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10  0:38 BCM5704 performance questions Ben Greear
2005-06-09 23:56 ` Michael Chan [this message]
2005-06-10  1:24   ` Ben Greear
2005-06-10  0:37     ` Michael Chan
2005-06-10 21:09       ` Ben Greear
2005-06-10 21:16         ` Michael Chan
2005-06-10 22:35           ` Ben Greear
2005-06-10 22:43             ` David S. Miller
2005-06-10 21:33         ` Rick Jones
2005-06-10 21:56           ` Ben Greear
2005-06-10 22:03             ` Rick Jones
2005-06-10 22:25               ` Ben Greear
2005-06-10 14:03   ` Jason Lunz
2005-06-10  0:54 ` David S. Miller
2005-06-10  1:20   ` Ben Greear
2005-06-10  1:29     ` David S. Miller
2005-06-10  2:28       ` Ben Greear

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=1118361376.5838.20.camel@rh4 \
    --to=mchan@broadcom.com \
    --cc=greearb@candelatech.com \
    --cc=netdev@oss.sgi.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 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.