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.93] Fourth test release of Tigon3 driver
Date: Fri, 01 Mar 2002 07:28:31 -0800 (PST) [thread overview]
Message-ID: <20020301.072831.120445660.davem@redhat.com> (raw)
Hey kiddies, uncle DaveM has a new release for ya:
ftp://ftp.kernel.org/pub/linux/kernel/people/davem/TIGON3/tg3-0.93.patch.gz
Changes in this release:
[FIX] Fix minimum MTU enforcement and streamline Jumbo handling
(Jeff)
[FEATURE] Acenic gets VLAN hw acceleration support. (DaveM)
[FEATURE] 8139CP gets VLAN hw acceleration support. (Jeff)
[FEATURE] 8139CP gets MTU changing updates. (Jeff)
[FEATURE] 8139CP gets RX checksum offload. (Jeff)
[FIX] Do not program Tigon3 MTU if it is not up yet. (DaveM)
[API] VLAN hw acceleration interfaces enhanced:
1) netdev->vlan_rx_register returns now a void, it cannot fail
2) Add NETIF_F_HW_VLAN_FILTER and netdev->vlan_rx_add_vid
for RX VLAN vid filtering acceleration as discussed
yesterday on this list.
3) VLAN layer does destroy the VLAN group when the last VLAN
device in it is unregistered. Implemented for hw
acceleration by calling vlan_rx_register with NULL group
argument.
[CLEANUP] Lots of private vlan kruft moved from
include/linux/if_vlan.h to net/8021q/vlan.h
Lots of totally unused stuff deleted.
[FIX] All the locking in the 8021q code has been audited, fixed, and
cleaned up.
Also fix refcounting, once VLAN device is made the reference to
its' hardware device is leaked forever. Good luck bringing
down any interface that had VLANs attached :( This bug has been
in the VLAN code since it went into the tree.
[FEATURE] Use a small hash table for VLAN group lookups.
[FEATURE] Add Robert Olsson's packet generator for stress testing.
See Documentation/networking/pktgen.txt for how to use it.
Soon I will add Robert's enhancements for bundling, this
is just the older basic version.
[FIX] Kill work limit code, this could cause a situation that leaves
the receive ring empty which deadlocks the Tigon3 and we never
get any new RX interrupts so it remains empty forever.
This is hoped to fix a hang condition reported by Lennert
Buytenhek. He was using Robert's packet generator which is
one of the reasons I have integrated it :-)
[FIX] Tigon3 TX vlan tagging improperly implemented. VLANs fully
tested with Tigon3 and appear to work :-)
Bugs known to not be fixed in this release:
[BUG] 5703 revision chips do not work at all.
I will work on that soon, hopefully.
Please test it hard, and if you find some problem not listed in the
"not fixed yet" bug list do let us know about it. Do not hesitate to
report "yeah it works, here is my setup" cases, I do log them and they
do help us know what kind of coverage the driver is getting and
exactly which chips have been tested.
Thanks.
next reply other threads:[~2002-03-01 15:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 15:28 David S. Miller [this message]
2002-03-01 16:11 ` Various 802.1Q VLAN driver patches Ben Greear
2002-03-01 16:11 ` David S. Miller
2002-03-01 16:27 ` Various 802.1Q VLAN driver patches. [try2] Ben Greear
2002-03-01 16:30 ` Matti Aarnio
2002-03-01 16:33 ` Randy.Dunlap
2002-03-01 16:42 ` Jeff Garzik
2002-03-01 17:14 ` Various 802.1Q VLAN driver patches. [try3] Ben Greear
2002-03-01 19:24 ` Jeff Garzik
2002-03-01 16:35 ` Various 802.1Q VLAN driver patches. [try2] Jeff Garzik
2002-03-01 16:46 ` Andreas Ferber
2002-03-01 18:45 ` Andrew Morton
2002-03-01 18:50 ` David S. Miller
2002-03-01 19:02 ` Jeff Garzik
2002-03-01 21:00 ` Alan Cox
2002-03-01 20:53 ` Jeff Garzik
2002-03-01 21:10 ` David S. Miller
2002-03-01 19:09 ` Jeff Garzik
2002-03-01 20:34 ` Andreas Ferber
2002-03-01 20:51 ` Jeff Garzik
2002-03-01 21:19 ` Ben Greear
2002-03-01 21:19 ` David S. Miller
2002-03-01 21:51 ` Andreas Ferber
2002-03-01 16:40 ` David S. Miller
2002-03-01 19:17 ` Various 802.1Q VLAN driver patches Jeff Garzik
2002-03-01 19:44 ` Patrick Schaaf
2002-03-01 19:43 ` Jeff Garzik
2002-03-03 20:16 ` Teodor Iacob
2002-03-01 20:27 ` Donald Becker
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=20020301.072831.120445660.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