From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: "David A. Ranch" <dranch@juniper.net>
Cc: e1000-devel@lists.sourceforge.net, Daniel Drake <dsd@gentoo.org>,
Jeff Garzik <jeff@garzik.org>, netdev <netdev@vger.kernel.org>
Subject: Re: e1000 and ICH9 hardware
Date: Mon, 29 Oct 2007 09:19:48 -0700 [thread overview]
Message-ID: <47260824.9070109@intel.com> (raw)
In-Reply-To: <472603F7.8060802@juniper.net>
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
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-10-29 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 13:33 e1000 and ICH9 hardware Daniel Drake
2007-10-29 14:45 ` Jeff Garzik
2007-10-29 16:01 ` David A. Ranch
2007-10-29 16:19 ` Kok, Auke [this message]
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=47260824.9070109@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=dranch@juniper.net \
--cc=dsd@gentoo.org \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--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).