From: Ben Hutchings <bhutchings@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-net-drivers@solarflare.com>
Subject: [PATCHv2 net-next 0/8] RX NFC support for hash-based filters
Date: Tue, 3 Jan 2012 21:56:59 +0000 [thread overview]
Message-ID: <1325627819.2832.31.camel@bwh-desktop> (raw)
1. Fix gianfar's validation of filter rule locations. In the previous
version of this series, this was a requirement for part 2, but that's
no longer the case.
2. Extend ethtool RX NFC rules API to support hash-based filter hardware
in which rule locations should be selected by the driver or firmware.
3. Change the sfc driver to implement this API instead of RX n-tuple.
4. Remove support for RX n-tuple, now that there are no in-tree
implementations.
Ben.
Ben Hutchings (8):
gianfar: Reject out-of-range RX NFC locations
ethtool: Allow drivers to select RX NFC rule locations
sfc: Change filter ID generation to satisfy priority semantics of RX
NFC
sfc: Use consistent types for filter IDs, indices and search depths
sfc: Add support for retrieving and removing filters by ID
sfc: Implement ethtool RX NFC rules API instead of n-tuple API
sfc: Remove now-unused filter function
ethtool: Remove ethtool_ops::set_rx_ntuple operation
drivers/net/ethernet/freescale/gianfar_ethtool.c | 5 +-
drivers/net/ethernet/sfc/efx.h | 16 +-
drivers/net/ethernet/sfc/ethtool.c | 188 +++++++++++---
drivers/net/ethernet/sfc/filter.c | 310 +++++++++++++++++++---
drivers/net/ethernet/sfc/filter.h | 12 +
include/linux/ethtool.h | 30 ++-
net/core/ethtool.c | 66 +----
net/socket.c | 2 +-
8 files changed, 484 insertions(+), 145 deletions(-)
--
1.7.4.4
--
Ben Hutchings, Staff Engineer, Solarflare
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:[~2012-01-03 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 21:56 Ben Hutchings [this message]
2012-01-03 21:59 ` [PATCHv2 net-next 1/8] gianfar: Reject out-of-range RX NFC locations Ben Hutchings
2012-01-03 22:04 ` [PATCHv2 net-next 2/8] ethtool: Allow drivers to select RX NFC rule locations Ben Hutchings
2012-01-03 22:05 ` [PATCHv2 net-next 3/8] sfc: Change filter ID generation to satisfy priority semantics of RX NFC Ben Hutchings
2012-01-03 22:05 ` [PATCHv2 net-next 4/8] sfc: Use consistent types for filter IDs, indices and search depths Ben Hutchings
2012-01-03 22:05 ` [PATCHv2 net-next 5/8] sfc: Add support for retrieving and removing filters by ID Ben Hutchings
2012-01-03 22:05 ` [PATCHv2 net-next 6/8] sfc: Implement ethtool RX NFC rules API instead of n-tuple API Ben Hutchings
2012-01-03 22:05 ` [PATCHv2 net-next 7/8] sfc: Remove now-unused filter function Ben Hutchings
2012-01-03 22:07 ` [PATCHv2 net-next 8/8] ethtool: Remove ethtool_ops::set_rx_ntuple operation Ben Hutchings
2012-01-03 22:24 ` [PATCHv2 ethtool 1/3] ethtool-copy.h: sync with net-next Ben Hutchings
2012-01-03 22:24 ` [PATCHv2 ethtool 2/3] rxclass: Use RX_CLS_LOC_{ANY,SPECIAL} in place of RX_CLS_LOC_UNSPEC Ben Hutchings
2012-01-03 22:25 ` [PATCHv2 ethtool 3/3] rxclass: Allow driver to select RX NFC rule location Ben Hutchings
2012-01-04 19:11 ` [PATCHv2 net-next 0/8] RX NFC support for hash-based filters David Miller
2012-01-04 21:39 ` Ben Hutchings
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=1325627819.2832.31.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-net-drivers@solarflare.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).