From: "David S. Miller" <davem@redhat.com>
To: "Michael Chan" <mchan@broadcom.com>
Cc: gnb@sgi.com, netdev@oss.sgi.com
Subject: Re: [PATCH] fix BUG in tg3_tx
Date: Wed, 26 May 2004 11:47:14 -0700 [thread overview]
Message-ID: <20040526114714.23fcf37d.davem@redhat.com> (raw)
In-Reply-To: <B1508D50A0692F42B217C22C02D849727FEDBE@NT-IRVA-0741.brcm.ad.broadcom.com>
On Wed, 26 May 2004 10:43:10 -0700
"Michael Chan" <mchan@broadcom.com> wrote:
> I would recommend tg3 to make the switch also.
Ok, I'll make it use DMA tx descriptors by default.
The checking for cases where we can't do on-chip TX desciptors
I'll keep around (albeit commented out) just in case we allow
this again in the future.
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/05/26 11:46:50-07:00 davem@nuts.davemloft.net
# [TG3]: Use HOST TXDs always.
#
# drivers/net/tg3.c
# 2004/05/26 11:46:42-07:00 davem@nuts.davemloft.net +9 -0
# [TG3]: Use HOST TXDs always.
#
diff -Nru a/drivers/net/tg3.c b/drivers/net/tg3.c
--- a/drivers/net/tg3.c 2004-05-26 11:46:57 -07:00
+++ b/drivers/net/tg3.c 2004-05-26 11:46:57 -07:00
@@ -7534,6 +7534,14 @@
udelay(50);
tg3_nvram_init(tp);
+ /* Always use host TXDs, it performs better in particular
+ * with multi-frag packets. The tests below are kept here
+ * as documentation should we change this decision again
+ * in the future.
+ */
+ tp->tg3_flags |= TG3_FLAG_HOST_TXDS;
+
+#if 0
/* Determine if TX descriptors will reside in
* main memory or in the chip SRAM.
*/
@@ -7541,6 +7549,7 @@
GET_ASIC_REV(tp->pci_chip_rev_id) == ASIC_REV_5705 ||
GET_ASIC_REV(tp->pci_chip_rev_id) == ASIC_REV_5750)
tp->tg3_flags |= TG3_FLAG_HOST_TXDS;
+#endif
grc_misc_cfg = tr32(GRC_MISC_CFG);
grc_misc_cfg &= GRC_MISC_CFG_BOARD_ID_MASK;
next prev parent reply other threads:[~2004-05-26 18:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 17:43 [PATCH] fix BUG in tg3_tx Michael Chan
2004-05-26 18:47 ` David S. Miller [this message]
2004-05-26 23:52 ` Greg Banks
2004-05-26 23:50 ` Greg Banks
-- strict thread matches above, loose matches on Subject: below --
2004-05-26 1:22 Michael Chan
2004-05-25 20:04 Michael Chan
2004-05-26 0:54 ` Greg Banks
2004-05-26 16:04 ` Greg Banks
2004-05-26 18:01 ` David S. Miller
2004-05-26 23:47 ` Greg Banks
2004-05-26 23:52 ` David S. Miller
2004-05-27 0:12 ` Greg Banks
2004-05-24 17:33 Michael Chan
2004-05-24 17:26 Michael Chan
2004-05-24 7:26 Greg Banks
2004-05-24 7:40 ` David S. Miller
2004-05-24 8:04 ` Greg Banks
2004-05-24 17:06 ` David S. Miller
2004-05-25 1:04 ` Greg Banks
2004-05-25 17:51 ` David S. Miller
2004-05-26 0:12 ` Greg Banks
2004-05-25 17:52 ` David S. Miller
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=20040526114714.23fcf37d.davem@redhat.com \
--to=davem@redhat.com \
--cc=gnb@sgi.com \
--cc=mchan@broadcom.com \
--cc=netdev@oss.sgi.com \
/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).