From: David Miller <davem@davemloft.net>
To: mcarlson@broadcom.com
Cc: dmitry.torokhov@gmail.com, eric.dumazet@gmail.com,
netdev@vger.kernel.org, jfeeney@redhat.com
Subject: Re: tg3 appears to be sick in 2.6.33
Date: Sun, 10 Jan 2010 13:52:42 -0800 (PST) [thread overview]
Message-ID: <20100110.135242.113292015.davem@davemloft.net> (raw)
In-Reply-To: <20100108194222.GA8386@xw6200.broadcom.net>
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?
Thanks.
next prev parent reply other threads:[~2010-01-10 21:52 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 [this message]
2010-01-11 17:59 ` Matt Carlson
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=20100110.135242.113292015.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=jfeeney@redhat.com \
--cc=mcarlson@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.