From: Jeff Garzik <jeff@garzik.org>
To: Ayyappan.Veeraiyan@intel.com
Cc: netdev@vger.kernel.org, arjan@linux.intel.com,
akpm@linux-foundation.org, auke-jan.h.kok@intel.com,
hch@infradead.org, shemminger@linux-foundation.org,
nhorman@tuxdriver.com, inaky@linux.intel.com, mb@bu3sch.de
Subject: Re: [PATCH 0/1] ixgbe: Support for Intel(R) 10GbE PCI Express adapters - Take #2
Date: Tue, 10 Jul 2007 14:00:49 -0400 [thread overview]
Message-ID: <4693C951.3040608@garzik.org> (raw)
In-Reply-To: <20070710174504.9615.10053.stgit@localhost.localdomain>
Ayyappan.Veeraiyan@intel.com wrote:
> 7. NAPI mode uses sigle Rx queue and so fake netdev usage is removed.
> 8. Non-NAPI mode is added.
Honestly I'm not sure about drivers that have both NAPI and non-NAPI paths.
Several existing drivers do this, and in almost every case, I tend to
feel the driver would benefit from picking one approach, rather than
doing both.
Doing both tends to signal that the author hasn't bothered to measure
the differences between various approaches, and pick a clear winner.
I strongly prefer NAPI combined with hardware interrupt mitigation -- it
helps with multiple net interfaces balance load across the system, at
times of high load -- but I'm open to other solutions as well.
So... what are your preferences? What is the setup that gets closest
to wire speed under Linux? :)
Jeff
next prev parent reply other threads:[~2007-07-10 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 17:45 [PATCH 0/1] ixgbe: Support for Intel(R) 10GbE PCI Express adapters - Take #2 Ayyappan.Veeraiyan
2007-07-10 17:49 ` [PATCH 1/1]ixgbe: Driver for Intel 82598 based 10GbE PCI Express family of adapters Ayyappan Veeraiyan
2007-07-10 18:00 ` Jeff Garzik [this message]
2007-07-10 18:11 ` [PATCH 0/1] ixgbe: Support for Intel(R) 10GbE PCI Express adapters - Take #2 Veeraiyan, Ayyappan
2007-07-10 18:23 ` Jeff Garzik
2007-07-17 13:22 ` Veeraiyan, Ayyappan
2007-07-23 18:52 ` Rick Jones
2007-07-26 20:07 ` Veeraiyan, Ayyappan
2007-07-26 20:20 ` Rick Jones
2007-07-10 18:47 ` 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=4693C951.3040608@garzik.org \
--to=jeff@garzik.org \
--cc=Ayyappan.Veeraiyan@intel.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=auke-jan.h.kok@intel.com \
--cc=hch@infradead.org \
--cc=inaky@linux.intel.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=shemminger@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.