From: Roger Luethi <rl@hellgate.ch>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 2.5] via-rhine 1.19-2.5: One more Rhine-I fix
Date: Mon, 14 Jul 2003 22:05:20 +0200 [thread overview]
Message-ID: <20030714200520.GB4774@k3.hellgate.ch> (raw)
In-Reply-To: <20030714200203.GA4774@k3.hellgate.ch>
[-- Attachment #1: Type: text/plain, Size: 139 bytes --]
This patch fixes another way the Rhine-I found to break down under load. It
should bring Rhine-I behavior on par with the Rhine-II.
Roger
[-- Attachment #2: via-rhine-1.19-2.5.diff --]
[-- Type: text/plain, Size: 1103 bytes --]
--- linux-2.5/drivers/net/via-rhine.c.org 2003-07-14 21:49:56.000000000 +0200
+++ linux-2.5/drivers/net/via-rhine.c 2003-07-14 21:50:09.000000000 +0200
@@ -122,11 +122,14 @@
- No filtering multicast in promisc mode (Edward Peng)
- Fix for Rhine-I Tx timeouts
+ LK1.1.19 (Roger Luethi)
+ - Increase Tx threshold for unspecified errors
+
*/
#define DRV_NAME "via-rhine"
-#define DRV_VERSION "1.1.18-2.5"
-#define DRV_RELDATE "July-4-2003"
+#define DRV_VERSION "1.1.19-2.5"
+#define DRV_RELDATE "July-12-2003"
/* A few user-configurable values.
@@ -1664,9 +1667,13 @@
}
if ((intr_status & IntrTxError) && ~( IntrTxAborted | IntrTxUnderrun |
IntrTxDescRace )) {
- if (debug > 2)
- printk(KERN_INFO "%s: Unspecified error.\n",
- dev->name);
+ if (np->tx_thresh < 0xE0) {
+ writeb(np->tx_thresh += 0x20, ioaddr + TxConfig);
+ }
+ if (debug > 1)
+ printk(KERN_INFO "%s: Unspecified error. Tx "
+ "threshold now %2.2x.\n",
+ dev->name, np->tx_thresh);
}
if (intr_status & ( IntrTxAborted | IntrTxUnderrun | IntrTxDescRace |
IntrTxError ))
prev parent reply other threads:[~2003-07-14 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 20:02 [PATCH 2.4] via-rhine 1.19: One more Rhine-I fix Roger Luethi
2003-07-14 20:05 ` Roger Luethi [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=20030714200520.GB4774@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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).