netdev - Re: [E1000-devel] e1000 and ICH9 hardware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <47260824.9070109@intel.com>
Date:	Mon, 29 Oct 2007 09:19:48 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	"David A. Ranch" <dranch@...iper.net>
CC:	Jeff Garzik <jeff@...zik.org>, e1000-devel@...ts.sourceforge.net,
	Daniel Drake <dsd@...too.org>, netdev <netdev@...r.kernel.org>
Subject: Re: [E1000-devel] e1000 and ICH9 hardware

David A. Ranch wrote:
>>> e1000 is being frozen in time as "pre-PCI Express e1000's".
>>   
> Asking the question a different way, will the current e1000 driver 
> continue to get new features, performance / power / optimization tweaks, 
> etc. or is most of the primary development be moving only on the e1000e kit?

the ultimate goal is to move all the pci-express hardware support over to e1000e.

since the pci/pci-x generation e1000 chipsets do not have nearly the amount of
features that the pci-e silicon has, you can expect the e1000 driver to be
significantly stripped down.

We do however want to keep any feature that is supported for the pci/pci-x
hardware in e1000 active. we will not disable TSO for instance. As for other
features we will decide whatever makes best sense for the hardware. (e.g. none of
the 8254x chipsets support multiple queues).

All of the primary development of features will focus on e1000e.

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