Jeff Garzik wrote:
Andrew Grover wrote:
I think making e1000new ICH9-and-newer isn't really the best place to
split it. The Windows e1000 driver got split on the PCI->PCIe
transition, something that clearly delineated what nics one driver
supported, and the other. There's no real technical reason for
splitting now other than "this was when e1000old collapsed under its
own weight".

The PCIe adapters are also the first ones to support multiple queues
IIRC, maybe that would be an another actual technical reason to split
it there?

Can knowledgeable people characterize the PCIe adapters somehow? Is that "ICH8-era and later", or does it go back further than that?

very brief outline:


all the pci-express adapters that are supported are extremely similar:

- they all support 2 queues
- the register sets are (almost entirely) identical
- there is minimal feature variance between 82571/2/3, esb2lan, ich8/9

The major differences between 82571/2/3, esb2lan and ich8/9 are PHY-based (4 different PHY's basically, one for 82571/2/3, one for esb2lan and 2 for ich8/9, excluding fiber and serdes here) and NVM/EEPROM.


ich8 and 9 are consistent with 82571/2/3 - on-board nic's based on the 82571 design with different PHY's, and added features for the newer demands. A driver split here would be possible but not justified IMHO.


this above discussion excludes the new server NIC hardware that we are about to release (aka 82575), which will have it's own driver, since the register set and descriptor types are completely different.

if you want a quick view of features by chipset type, open the patch and search forward to /e1000_setup_flags/. The list below shows historically which features were added from time to time. This one function that sets up all these features is a quick reference that easily shows the distinction between pre-pcie and pcie e1000 hardware.


Auke
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to