From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Mark McLoughlin <markmc@redhat.com>,
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
Andrew Grover <andy.grover@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jason Lunz <lunz@reflexsecurity.com>
Subject: Re: e1000: backport ich9 support from 7.5.5 ?
Date: Fri, 29 Jun 2007 19:31:55 -0700 [thread overview]
Message-ID: <4685C09B.7040908@intel.com> (raw)
In-Reply-To: <46859F3F.305@garzik.org>
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
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-06-30 2:31 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 17:29 e1000: backport ich9 support from 7.5.5 ? Mark McLoughlin
2007-06-29 17:50 ` Jason Lunz
2007-06-29 19:51 ` Kok, Auke
2007-06-29 20:22 ` Jason Lunz
2007-06-29 20:59 ` Jeff Garzik
2007-06-30 21:24 ` Mark McLoughlin
2007-07-02 23:52 ` Williams, Mitch A
2007-07-03 0:10 ` Rick Jones
2007-07-03 0:55 ` Jason Lunz
2007-07-03 1:44 ` Kok, Auke
2007-07-03 7:15 ` Christoph Hellwig
2007-07-03 13:13 ` [E1000-devel] " Jeff Garzik
2007-06-29 20:55 ` Jeff Garzik
2007-06-29 21:39 ` Kok, Auke
2007-06-29 22:03 ` Andrew Morton
2007-06-29 22:11 ` Jeff Garzik
2007-06-29 23:24 ` RFR: New e1000 driver (e1000new), was: " Kok, Auke
2007-06-29 23:38 ` Arjan van de Ven
2007-07-08 18:20 ` Jeff Garzik
2007-07-08 20:14 ` Arjan van de Ven
2007-07-08 22:01 ` [E1000-devel] " Jonathan Lundell
2007-06-30 3:32 ` Roland Dreier
2007-07-08 18:20 ` Jeff Garzik
2007-07-06 19:07 ` Jeff Garzik
2007-07-07 0:13 ` Kok, Auke
2007-07-07 12:23 ` James Chapman
2007-07-08 18:41 ` James Chapman
2007-07-07 18:59 ` Andrew Grover
2007-06-29 23:57 ` Andrew Grover
2007-06-30 0:02 ` Andrew Grover
2007-06-30 0:09 ` Jeff Garzik
2007-06-30 1:29 ` Jim McCullough
2007-06-30 1:31 ` Jim McCullough
2007-06-30 2:34 ` [E1000-devel] " Kok, Auke
2007-06-30 2:31 ` Kok, Auke [this message]
2007-06-30 8:25 ` Christoph Hellwig
2007-07-03 22:48 ` Splitting e1000 (Was: Re: e1000: backport ich9 support from 7.5.5 ?) Kok, Auke
2007-07-05 18:32 ` Kok, Auke
2007-07-06 0:22 ` Jeff Garzik
2007-07-07 0:14 ` Kok, Auke
2007-07-07 13:58 ` James Chapman
2007-07-07 19:04 ` Francois Romieu
2007-07-07 21:54 ` Kok, Auke
2007-07-08 1:32 ` Stephen Hemminger
2007-07-08 10:07 ` James Chapman
2007-07-08 16:29 ` Arjan van de Ven
2007-07-08 18:06 ` Jeff Garzik
2007-07-08 19:24 ` Andrew Grover
2007-07-09 17:56 ` Jeff Garzik
2007-07-08 20:05 ` Arjan van de Ven
2007-07-09 18:39 ` Jeff Garzik
2007-07-09 18:46 ` Stephen Hemminger
2007-07-09 19:36 ` Arjan van de Ven
2007-07-09 20:46 ` Kok, Auke
2007-07-09 22:26 ` Jeff Garzik
2007-07-13 21:45 ` Kok, Auke
2007-07-13 22:08 ` Jeff Garzik
2007-07-13 22:13 ` Kok, Auke
2007-07-08 18:08 ` Jeff Garzik
2007-07-08 17:41 ` Jeff Garzik
2007-06-30 14:31 ` e1000: backport ich9 support from 7.5.5 ? James Chapman
2007-06-30 16:29 ` Kok, Auke
2007-07-01 10:45 ` James Chapman
2007-06-30 8:26 ` Christoph Hellwig
2007-06-29 22:16 ` Kok, Auke
2007-06-29 22:07 ` Jeff Garzik
2007-06-29 21:39 ` Andy Gospodarek
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=4685C09B.7040908@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andy.grover@gmail.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=lunz@reflexsecurity.com \
--cc=markmc@redhat.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).