From: David Miller <davem@davemloft.net>
To: macro@linux-mips.org
Cc: netdev@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] declance: Restore tx descriptor ring locking
Date: Mon, 08 Jun 2009 02:42:53 -0700 (PDT) [thread overview]
Message-ID: <20090608.024253.54091368.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.1.10.0906080219360.6360@ftp.linux-mips.org>
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Mon, 8 Jun 2009 02:47:05 +0100 (WEST)
> A driver overhaul on 29 Feb 2000 (!) broke locking around fiddling with
> the tx descriptor ring in start_xmit(); a follow-on "fix" removed the
> broken remnants altogether. Here's a patch to restore proper locking in
> the function -- the complement in the interrupt handler has been correct
> all the time.
>
> This *may* have been the reason for the occasional confusion of the chip
> -- triggering a tx timeout followed by a chip reset sequence -- seen on
> R4k-based DECstations with the onboard Ethernet interface. Another theory
> is the confusion is due to an unindentified problem -- perhaps a silicon
> erratum -- associated with the variation of the MT ASIC used to interface
> the R4k CPU to the rest of the system on these computers; with its
> aggressive write-back buffering the design is particularly weakly ordered
> when it comes to MMIO (in the absence of ordering barriers uncached reads
> are allowed to bypass earlier uncached writes, even if to the same
> location), which may trigger all kinds of corner cases in peripheral
> hardware as well as software.
>
> Either way this piece of code is buggy.
>
> Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>
Looks good to me, applied.
prev parent reply other threads:[~2009-06-08 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 1:47 [PATCH] declance: Restore tx descriptor ring locking Maciej W. Rozycki
2009-06-08 9:42 ` David Miller [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=20090608.024253.54091368.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--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).