From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: NetDev <netdev@vger.kernel.org>
Cc: Jeff Garzik <jgarzik@pobox.com>, "David S. Miller" <davem@davemloft.net>
Subject: [PATCHES] RFC: Ethtool patches to add multi queue support, LRO
Date: Tue, 31 Jul 2007 13:20:23 -0700 [thread overview]
Message-ID: <46AF9987.3060007@intel.com> (raw)
All,
Recently new features have been written to add multiqueue support and LRO.
However, none of the patches touch on a basic configuration scheme and most use
module parameters.
I propose several patches to add support to change these features for LRO and
multiqueue. Currently these patches are implemented in the most generic way
possible (largely copy/paste from current ethtool code) - and add 'ethtool -k
lro on|off' support that toggles the NETIF_F_LRO generic device flag, and a new
ethtool_queueparam struct to get/pass rx and tx queue count.
I'm contenplating adding a "usecs-irq" non-rx non-tx parameter for the intel
(1/10) gigabit adapters since our adapters share an interrupt moderation
counters for both rx and tx, but that will come later.
Cheers,
Auke
reply other threads:[~2007-07-31 20:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46AF9987.3060007@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.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).