From: Alexander Duyck <alexander.h.duyck@intel.com>
To: davem@davemloft.net, jeffrey.t.kirsher@intel.com,
bhutchings@solarflare.com
Cc: netdev@vger.kernel.org
Subject: [net-next-2.6 PATCH 0/2] Start of work to cleanup ntuple filters
Date: Fri, 08 Apr 2011 15:07:16 -0700 [thread overview]
Message-ID: <20110408220410.25468.49130.stgit@gitlad.jf.intel.com> (raw)
This patch series is the start of my work to cleanup ntuple filters and the
way they are implemented in ixgbe. These first two patches lay the groundwork
for moving ixgbe over to using the network flow classifier interface instead
of the ntuple interface.
This will eventually allow for ixgbe to be able to maintain its own rule list,
add support for removal of filters, and will correct the multiple display
issues seen with ntuple filters.
---
Alexander Duyck (2):
ethtool: add ntuple flow specifier data to network flow classifier
ethtool: prevent null pointer dereference with NTUPLE set but no set_rx_ntuple
include/linux/ethtool.h | 52 +++++++++++++++++++++++++++++------------------
net/core/ethtool.c | 3 +++
net/socket.c | 14 ++++++-------
3 files changed, 42 insertions(+), 27 deletions(-)
--
next reply other threads:[~2011-04-08 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 22:07 Alexander Duyck [this message]
2011-04-08 22:07 ` [net-next-2.6 PATCH 1/2] ethtool: prevent null pointer dereference with NTUPLE set but no set_rx_ntuple Alexander Duyck
2011-04-11 20:21 ` David Miller
2011-04-08 22:07 ` [net-next-2.6 PATCH 2/2] ethtool: add ntuple flow specifier data to network flow classifier Alexander Duyck
2011-04-08 22:21 ` Ben Hutchings
2011-04-08 22:35 ` Alexander Duyck
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=20110408220410.25468.49130.stgit@gitlad.jf.intel.com \
--to=alexander.h.duyck@intel.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@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).