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 17:37:41 -0700 [thread overview]
Message-ID: <1118363861.5838.29.camel@rh4> (raw)
In-Reply-To: <42A8EBDA.6010306@candelatech.com>
On Thu, 2005-06-09 at 18:24 -0700, Ben Greear wrote:
> Michael Chan wrote:
> >
> > 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 any way I can tell which systems are affected? It won't be
> an option for me to purposefully ship possibly busted drivers/hardware,
> but if I can be certain that my systems are immune, I will try this
> modification.
>
I mentioned this so that you could verify that the slow performance was
indeed caused by ONE_DMA. Even if your system is affected, it's a very
subtle problem that won't show up right away and should allow you to get
some performance numbers.
Unfortunately, if indeed it is ONE_DMA, there is no easy way for us to
tell which system is affected. And the recommendation is to turn it on
for all 5704 in PCIX 100/133.
next prev parent reply other threads:[~2005-06-10 0:37 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
2005-06-10 1:24 ` Ben Greear
2005-06-10 0:37 ` Michael Chan [this message]
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=1118363861.5838.29.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.