netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matt Carlson" <mcarlson@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: "Matthew Carlson" <mcarlson@broadcom.com>,
	"dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
	"eric.dumazet@gmail.com" <eric.dumazet@gmail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"jfeeney@redhat.com" <jfeeney@redhat.com>
Subject: Re: tg3 appears to be sick in 2.6.33
Date: Mon, 11 Jan 2010 09:59:11 -0800	[thread overview]
Message-ID: <20100111175911.GA10496@xw6200.broadcom.net> (raw)
In-Reply-To: <20100110.135242.113292015.davem@davemloft.net>

On Sun, Jan 10, 2010 at 01:52:42PM -0800, David Miller wrote:
> From: "Matt Carlson" <mcarlson@broadcom.com>
> Date: Fri, 8 Jan 2010 11:42:22 -0800
> 
> > [PATCH] tg3: Fix std rx prod ring handling
> > 
> > There are some tg3 devices that require the driver to post new rx
> > buffers in smaller increments.  Commit
> > 4361935afe3abc3e5a93006b99197fac1fabbd50, "tg3: Consider
> > rx_std_prod_idx a hw mailbox" changed how the driver tracks the rx
> > producer ring updates, but it does not make any special considerations
> > for the above-mentioned devices.  For those devices, it is possible for
> > the driver to hit the special case path, which updates the hardware
> > mailbox register but skips updating the shadow software mailbox member.
> > If the special case path represents the final mailbox update for this
> > ISR iteration, the hardware and software mailbox values will be out of
> > sync.  Ultimately, this will cause the driver to use a stale mailbox
> > value on the next iteration, which will appear to the hardware as a
> > large rx buffer update.  Bad things ensue.
> > 
> > The fix is to update the software shadow mailbox member when the special
> > case path is taken.
> > 
> > Signed-off-by: Matt Carlson <mcarlson@broadcom.com>
> 
> Matt, since we have positive testing, want me to apply this?

I have a small patchset queued up for net-2.6.  Let me just include this
one into the mix and submit it all at once.


  reply	other threads:[~2010-01-11 17:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 19:56 tg3 appears to be sick in 2.6.33 Dmitry Torokhov
2010-01-07 20:48 ` Matt Carlson
2010-01-07 22:24   ` Eric Dumazet
2010-01-07 22:45     ` Dmitry Torokhov
2010-01-07 23:53       ` Matt Carlson
2010-01-08  0:14         ` Dmitry Torokhov
2010-01-08  1:36           ` Dmitry Torokhov
2010-01-08 18:09             ` Matt Carlson
2010-01-08 18:25               ` Dmitry Torokhov
2010-01-08 19:42                 ` Matt Carlson
2010-01-08 22:50                   ` Dmitry Torokhov
2010-01-09  6:30                     ` Dmitry Torokhov
2010-01-10 21:52                   ` David Miller
2010-01-11 17:59                     ` Matt Carlson [this message]
2010-01-11 21:39                       ` David Miller
2010-01-07 22:52 ` Matt Carlson
2010-01-07 23:23   ` Dmitry Torokhov

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=20100111175911.GA10496@xw6200.broadcom.net \
    --to=mcarlson@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jfeeney@redhat.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 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).