From: Andrew Rybchenko <arybchenko@solarflare.com>
To: <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH 00/11] net/sfc: support flow API RSS action
Date: Wed, 30 Aug 2017 19:17:30 +0100 [thread overview]
Message-ID: <1504117061-17906-1-git-send-email-arybchenko@solarflare.com> (raw)
Few base driver patches have checkpatches.sh errors due to difference
in coding conventions.
Andrew Rybchenko (1):
net/sfc: use RSS key size define from base driver
Ivan Malov (3):
net/sfc: fix unused variable warnings in RSS-agnostic build
net/sfc/base: add RSS key size define to efx.h
net/sfc: add support for the flow API RSS action
Mark Spender (7):
net/sfc/base: define a handle to denote default RSS context
net/sfc/base: fix default RSS context check on Siena
net/sfc/base: add the max. number of RSS exclusive contexts
net/sfc/base: rename API to check Rx scale and hash support
net/sfc/base: add API to allocate and free RSS contexts
net/sfc/base: update RSS API to take RSS context parameter
net/sfc/base: add API to set an RSS context for a filter
doc/guides/nics/sfc_efx.rst | 2 +
drivers/net/sfc/base/ef10_filter.c | 16 +++-
drivers/net/sfc/base/ef10_impl.h | 15 +++
drivers/net/sfc/base/ef10_rx.c | 96 +++++++++++++++----
drivers/net/sfc/base/efx.h | 40 ++++++--
drivers/net/sfc/base/efx_filter.c | 35 +++++--
drivers/net/sfc/base/efx_impl.h | 20 ++--
drivers/net/sfc/base/efx_rx.c | 142 ++++++++++++++++++++++++----
drivers/net/sfc/base/hunt_nic.c | 7 ++
drivers/net/sfc/base/medford_nic.c | 7 ++
drivers/net/sfc/base/siena_nic.c | 3 +
drivers/net/sfc/sfc.c | 14 ++-
drivers/net/sfc/sfc.h | 6 +-
drivers/net/sfc/sfc_ethdev.c | 19 ++--
drivers/net/sfc/sfc_flow.c | 188 ++++++++++++++++++++++++++++++++++++-
drivers/net/sfc/sfc_flow.h | 15 +++
drivers/net/sfc/sfc_rx.c | 34 +++++--
17 files changed, 563 insertions(+), 96 deletions(-)
--
1.8.2.3
next reply other threads:[~2017-08-30 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 18:17 Andrew Rybchenko [this message]
2017-08-30 18:17 ` [dpdk-dev] [PATCH 01/11] net/sfc: fix unused variable warnings in RSS-agnostic build Andrew Rybchenko
2017-08-30 18:17 ` [dpdk-dev] [PATCH 02/11] net/sfc/base: define a handle to denote default RSS context Andrew Rybchenko
2017-08-30 18:17 ` [dpdk-dev] [PATCH 03/11] net/sfc/base: fix default RSS context check on Siena Andrew Rybchenko
2017-08-30 18:17 ` [dpdk-dev] [PATCH 04/11] net/sfc/base: add the max. number of RSS exclusive contexts Andrew Rybchenko
2017-08-30 18:17 ` [dpdk-dev] [PATCH 05/11] net/sfc/base: rename API to check Rx scale and hash support Andrew Rybchenko
2017-08-30 18:17 ` [dpdk-dev] [PATCH 06/11] net/sfc/base: add API to allocate and free RSS contexts Andrew Rybchenko
2017-08-30 18:17 ` [dpdk-dev] [PATCH 07/11] net/sfc/base: update RSS API to take RSS context parameter Andrew Rybchenko
2017-08-30 18:17 ` [dpdk-dev] [PATCH 08/11] net/sfc/base: add API to set an RSS context for a filter Andrew Rybchenko
2017-08-30 18:17 ` [dpdk-dev] [PATCH 09/11] net/sfc/base: add RSS key size define to efx.h Andrew Rybchenko
2017-08-30 18:17 ` [dpdk-dev] [PATCH 10/11] net/sfc: use RSS key size define from base driver Andrew Rybchenko
2017-08-30 18:17 ` [dpdk-dev] [PATCH 11/11] net/sfc: add support for the flow API RSS action Andrew Rybchenko
2017-09-01 16:27 ` [dpdk-dev] [PATCH 00/11] net/sfc: support " Ferruh Yigit
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=1504117061-17906-1-git-send-email-arybchenko@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.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).