From: Jeff Garzik <jgarzik@pobox.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
NetDev <netdev@vger.kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>,
"Ronciak, John" <john.ronciak@intel.com>
Subject: Re: RFC/Progress update: e1000e pci-express -only e1000 driver
Date: Sat, 28 Jul 2007 14:07:55 -0400 [thread overview]
Message-ID: <46AB85FB.10102@pobox.com> (raw)
In-Reply-To: <p73sl78r5yu.fsf@bingen.suse.de>
Andi Kleen wrote:
> "Kok, Auke" <auke-jan.h.kok@intel.com> writes:
>
>> * Removed all multi-queue code
>
> Why? With David's new multi NAPI work it will finally make sense, won't it?
It will come back, most definitely.
Not speaking for Auke, but I'm pretty sure this falls under the category
of "start small and simple, get it into the tree rapidly."
Jeff
next prev parent reply other threads:[~2007-07-28 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 21:12 RFC/Progress update: e1000e pci-express -only e1000 driver Kok, Auke
2007-07-28 13:52 ` Andi Kleen
2007-07-28 18:07 ` Jeff Garzik [this message]
2007-07-28 18:18 ` Kok, Auke
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=46AB85FB.10102@pobox.com \
--to=jgarzik@pobox.com \
--cc=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=auke-jan.h.kok@intel.com \
--cc=john.ronciak@intel.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).