From: "Matt Carlson" <mcarlson@broadcom.com>
To: "Ben Hutchings" <bhutchings@solarflare.com>
Cc: "Matthew Carlson" <mcarlson@broadcom.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Michael Chan" <mchan@broadcom.com>
Subject: Re: [PATCH net-next 2/2] tg3: Scale back code that modifies MRRS
Date: Mon, 28 Nov 2011 14:45:58 -0800 [thread overview]
Message-ID: <20111128224558.GA20447@mcarlson.broadcom.com> (raw)
In-Reply-To: <1322510036.26733.12.camel@bwh-desktop>
On Mon, Nov 28, 2011 at 11:53:56AM -0800, Ben Hutchings wrote:
> On Mon, 2011-11-28 at 11:41 -0800, Matt Carlson wrote:
> > Tg3 normally gets a performance boost by increasing the PCI Maximum Read
> > Request Size (MRRS) to 4k. Unfortunately, this is causing some problems
> > on particular hardware platforms. This patch removes all code that
> > modifies the MRRS except for one case.
> >
> > As part of a solution to fix an internal FIFO problem on the 5719, the
> > driver artificially capped the MRRS to 2k for the entire 5719, and later
> > 5720, ASIC revs. This was overly aggressive and only really needed to
> > be done for the 5719 A0. In the spirit of the rest of this patch, the
> > driver will only reprogram the MRRS for this device if the value exceeds
> > the 2k cap.
> [...]
>
> It may be better to do this as a PCI quirk, so that the generic MPS/MRRS
> configuration code has this information.
If at all possible, I'd rather do that as a follow-on patch. This patch
fixes a critical problem that is blocking a lot of testing.
prev parent reply other threads:[~2011-11-28 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 19:41 [PATCH net-next 2/2] tg3: Scale back code that modifies MRRS Matt Carlson
2011-11-28 19:53 ` Ben Hutchings
2011-11-28 22:45 ` Matt Carlson [this message]
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=20111128224558.GA20447@mcarlson.broadcom.com \
--to=mcarlson@broadcom.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@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 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.