Re: RFC: Evolution of the em driver
- From: Jeremy Chadwick <koitsu@xxxxxxxxxxx>
- Date: Wed, 31 Oct 2007 01:16:39 -0700
On Tue, Oct 30, 2007 at 09:06:39PM -0600, Scott Long wrote:
There are too many examples to name in every OS of drivers that have
tried in vain to support diverging hardware evolutionary paths. if_dc
and if_bge are great (or horrible, depending on your perspective)
examples of this in FreeBSD. My vote is to nip the madness in the bud
on if_em and have two (or more drivers) that support their hardware
families well instead of one driver that supports multiple families
marginally.
For what it's worth, I agree with Scott. I'd rather see a new and
separate driver (presumably igb(4)) than a "hacked up" em(4) driver
trying to handle tons of IC revisions. A good example of the insanity
the latter causes is nve(4) vs. nfe(4). :-)
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: RFC: Evolution of the em driver
- From: Peter Jeremy
- Re: RFC: Evolution of the em driver
- References:
- RFC: Evolution of the em driver
- From: Jack Vogel
- Re: RFC: Evolution of the em driver
- From: gnn
- Re: RFC: Evolution of the em driver
- From: Jack Vogel
- Re: RFC: Evolution of the em driver
- From: Scott Long
- RFC: Evolution of the em driver
- Prev by Date: Re: misc/117711: rpcbind binds to all interfaces on random ports even when using the -h flag
- Next by Date: Re: em watchdogs - OS involvement
- Previous by thread: Re: RFC: Evolution of the em driver
- Next by thread: Re: RFC: Evolution of the em driver
- Index(es):
Relevant Pages
- Re: RFC: Evolution of the em driver
... tried in vain to support diverging hardware evolutionary paths. ... My vote
is to nip the madness in the bud ... on if_em and have two (or more drivers) that support
their hardware ... families well instead of one driver that supports multiple families
... (freebsd-current) - Re: RFC: Evolution of the em driver
... tried in vain to support diverging hardware evolutionary paths. ... My vote
is to nip the madness in the bud ... on if_em and have two (or more drivers) that support
their hardware ... families well instead of one driver that supports multiple families
... (freebsd-stable)