From: Ben Hutchings <bhutchings@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
sf-linux-drivers <linux-net-drivers@solarflare.com>,
Tom Herbert <therbert@google.com>
Subject: pull request: sfc-next-2.6 2011-02-18
Date: Fri, 18 Feb 2011 16:00:39 +0000 [thread overview]
Message-ID: <1298044839.2570.7.camel@bwh-desktop> (raw)
The following changes since commit f878b995b0f746f5726af9e66940f3bf373dae91:
Merge branch 'for-davem' of git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc-next-2.6 (2011-02-15 12:25:19 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc-next-2.6.git for-davem
Add support for RFS acceleration in the sfc driver, and allow it to be
enabled and disabled dynamically using ethtool.
Ben.
Ben Hutchings (3):
net: RPS: Make hardware-accelerated RFS conditional on NETIF_F_NTUPLE
sfc: Limit filter search depth further for performance hints (i.e. RFS)
sfc: Implement hardware acceleration of RFS
drivers/net/sfc/efx.c | 49 +++++++++++++++++-
drivers/net/sfc/efx.h | 15 +++++
drivers/net/sfc/filter.c | 117 ++++++++++++++++++++++++++++++++++++++++--
drivers/net/sfc/net_driver.h | 3 +
net/core/dev.c | 3 +-
5 files changed, 180 insertions(+), 7 deletions(-)
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next reply other threads:[~2011-02-18 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 16:00 Ben Hutchings [this message]
2011-02-18 16:03 ` [PATCH net-next-2.6 1/3] net: RPS: Make hardware-accelerated RFS conditional on NETIF_F_NTUPLE Ben Hutchings
2011-02-18 16:03 ` [PATCH net-next-2.6 2/3] sfc: Limit filter search depth further for performance hints (i.e. RFS) Ben Hutchings
2011-02-18 16:04 ` [PATCH net-next-2.6 3/3] sfc: Implement hardware acceleration of RFS Ben Hutchings
2011-02-22 18:22 ` pull request: sfc-next-2.6 2011-02-18 David Miller
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=1298044839.2570.7.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
/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).