From: "David S. Miller" <davem@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: jgarzik@mandrakesoft.com, linux-net@vger.kernel.org
Subject: [BETA-0.95] Sixth test release of Tigon3 driver
Date: Tue, 05 Mar 2002 03:13:12 -0800 (PST) [thread overview]
Message-ID: <20020305.031312.92586410.davem@redhat.com> (raw)
0.94 turned out to be the "not quite Ginseng" release, but lets try to
rectify that :-)
This is the "praying for powder snow up in Tahoe" release, or TAHOE
for short. Get it at:
ftp://ftp.kernel.org/pub/linux/kernel/people/davem/TIGON3/tg3-0.95.patch.gz
[FIX] If we have to check the MAC_STAT register for link changes,
do not do it from interrupts. Do it from a timer instead.
Hey maybe the Dell onboard Tigon3 problems are fixed for real
now. :-)
[FIX] Off by one error in tg3_alloc_rx_skb() can lead to OOPS on
ifdown.
[FIX] 5700 chip interrupt status reporting protocol is racey,
work around it.
[DEBUG] Add assertions to TX ring processing.
[NICETY] When link comes up, report negotiated flow control settings.
[FEATURE] Adaptive RX coalescing.
[FEATURE] Improved DMA bursting settings, major performance
improvement especially on non-x86 platforms (in particular
Alpha and Sparc64 should get 10MB/sec extra bandwidth out of
this).
[DOC] Add Configure.help entry for CONFIG_TIGON3
I'm really really really really really (NO, I MEAN REALLY) interested
in performance comparisons of our 0.95 driver vs. Broadcom's stuff.
But, there is one special condition if you report benchmark numbers.
If our driver is faster _AND_ you are an _Australian_ in _Australia_,
you must send Jeff and I a case of Victoria Bitter for a job well
done. :-))))))
Note that this thing is to Marcelo very soon. So get testing!
Franks a lot,
David S. Miller
davem@redhat.com
next reply other threads:[~2002-03-05 11:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 11:13 David S. Miller [this message]
2002-03-05 13:35 ` [BETA-0.95] Sixth test release of Tigon3 driver Thomas Langås
2002-03-05 13:52 ` David S. Miller
2002-03-05 14:02 ` Thomas Langås
2002-03-05 14:03 ` David S. Miller
2002-03-05 14:06 ` David S. Miller
2002-03-05 14:19 ` Thomas Langås
2002-03-05 15:02 ` David S. Miller
2002-03-05 14:30 ` Thomas Langås
2002-03-05 15:04 ` David S. Miller
2002-03-05 16:34 ` Thomas Langås
2002-03-05 16:30 ` Scott Laird
2002-03-05 16:52 ` Sebastian Heidl
2002-03-05 14:07 ` Thomas Langås
-- strict thread matches above, loose matches on Subject: below --
2002-03-05 14:39 Jacobsson James
2002-03-05 14:43 Jacobsson James
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=20020305.031312.92586410.davem@redhat.com \
--to=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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