From: Govindarajulu Varadarajan <_govind@gmx.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: ssujith@cisco.com, benve@cisco.com,
Govindarajulu Varadarajan <_govind@gmx.com>
Subject: [PATCH net-next v3 0/8] enic updates
Date: Mon, 23 Jun 2014 16:07:57 +0530 [thread overview]
Message-ID: <1403519885-4908-1-git-send-email-_govind@gmx.com> (raw)
This series fixes minor bugs and adds new features like Accelerated RFS,
busy_poll, tx clean-up in napi_poll.
Please apply it to net-next.
v3:
* While doing tx cleanup in napi, ignore budget and clean up all desc possible.
v2:
* Fix #ifdef coding style issue in '[PATCH 4/8] enic: alloc/free rx_cpu_rmap'
And [PATCH 5/8] enic: Add Accelerated RFS support'
Govindarajulu Varadarajan (7):
flow_keys: Record IP layer protocol in skb_flow_dissect()
enic: fix return value in _vnic_dev_cmd
enic: devcmd for adding IP 5 tuple hardware filters
enic: alloc/free rx_cpu_rmap
enic: Add Accelerated RFS support
enic: add low latency socket busy_poll support
enic: do tx cleanup in napi poll
Tony Camuso (1):
enic: fix lockdep around devcmd_lock
drivers/net/ethernet/cisco/enic/Makefile | 2 +-
drivers/net/ethernet/cisco/enic/enic.h | 43 +++-
drivers/net/ethernet/cisco/enic/enic_api.c | 4 +-
drivers/net/ethernet/cisco/enic/enic_clsf.c | 279 ++++++++++++++++++++++++++
drivers/net/ethernet/cisco/enic/enic_clsf.h | 19 ++
drivers/net/ethernet/cisco/enic/enic_dev.c | 80 ++++----
drivers/net/ethernet/cisco/enic/enic_dev.h | 4 +-
drivers/net/ethernet/cisco/enic/enic_main.c | 245 +++++++++++++++++-----
drivers/net/ethernet/cisco/enic/enic_res.c | 1 +
drivers/net/ethernet/cisco/enic/vnic_dev.c | 65 +++++-
drivers/net/ethernet/cisco/enic/vnic_dev.h | 2 +
drivers/net/ethernet/cisco/enic/vnic_devcmd.h | 5 +
drivers/net/ethernet/cisco/enic/vnic_enet.h | 2 +
drivers/net/ethernet/cisco/enic/vnic_rq.h | 122 +++++++++++
include/net/flow_keys.h | 14 ++
include/net/sch_generic.h | 2 +-
net/core/flow_dissector.c | 1 +
17 files changed, 786 insertions(+), 104 deletions(-)
create mode 100644 drivers/net/ethernet/cisco/enic/enic_clsf.c
create mode 100644 drivers/net/ethernet/cisco/enic/enic_clsf.h
--
2.0.0
next reply other threads:[~2014-06-23 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 10:37 Govindarajulu Varadarajan [this message]
2014-06-23 10:37 ` [PATCH net-next v3 1/8] flow_keys: Record IP layer protocol in skb_flow_dissect() Govindarajulu Varadarajan
2014-06-23 10:37 ` [PATCH net-next v3 2/8] enic: fix return value in _vnic_dev_cmd Govindarajulu Varadarajan
2014-06-23 10:38 ` [PATCH net-next v3 3/8] enic: devcmd for adding IP 5 tuple hardware filters Govindarajulu Varadarajan
2014-06-23 10:38 ` [PATCH net-next v3 4/8] enic: alloc/free rx_cpu_rmap Govindarajulu Varadarajan
2014-06-23 10:38 ` [PATCH net-next v3 5/8] enic: Add Accelerated RFS support Govindarajulu Varadarajan
2014-06-23 10:38 ` [PATCH net-next v3 6/8] enic: fix lockdep around devcmd_lock Govindarajulu Varadarajan
2014-06-23 10:38 ` [PATCH net-next v3 7/8] enic: add low latency socket busy_poll support Govindarajulu Varadarajan
2014-06-23 10:38 ` [PATCH net-next v3 8/8] enic: do tx cleanup in napi poll Govindarajulu Varadarajan
2014-06-23 21:40 ` [PATCH net-next v3 0/8] enic updates 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=1403519885-4908-1-git-send-email-_govind@gmx.com \
--to=_govind@gmx.com \
--cc=benve@cisco.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ssujith@cisco.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).