From: Shradha Shah <sshah@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-net-drivers@solarflare.com>
Subject: [PATCH net-next 00/14] sfc: Enabling EF10 Vf's, set up vswitching and bind the SFC driver to the VF's
Date: Wed, 6 May 2015 00:53:03 +0100 [thread overview]
Message-ID: <554957DF.2010307@solarflare.com> (raw)
This set of patches makes way for the implementation of EF10
SR-IOV driver starting with some cleanup code.
NIC specific SR-IOV functions are moved to their own header
and netdev_ops are made generic instead of being NIC specific
Next in line comes the patch to enable VF's using sriov_configure.
VEB vswitching hierarchy is set up next followed by patches to
prepare sfc driver to bind to enabled VF's
This is followed by patch to support use of shared RSS contexts
which makes VF's use shared RSS contexts in all cases.
Patch series ends with a patch to bind the sfc driver to the
enabled VF's which creates network interfaces corresponding to
the VF's.
Coming up soon are the patches to set_vf_mac, set_vf_config,
set_vf_vlan, vf_spoofcheck, etc.
These patches have been tested with and without CONFIG_SFC_SRIOV.
In the case of CONFIG_SFC_SRIOV=y enabling of VF's using
sriov_configure is also tested. The enabled VF's bind to the
installed sfc driver succesfully to create network interfaces.
In the case of CONFIG_SFC_SRIOV=n enabling of VF's using
sriov_configure returns the correct error message:
"Function not implemented".
Daniel Pieczko (5):
sfc: Move and rename efx_vf struct to siena_vf
sfc: Record [rt]x_dpcpu_fw_id in EF10 nic_data
sfc: record the PF's vport ID in nic_data
sfc: create VEB vswitch and vport above default firmware setup
sfc: get the PF number and record in nic_data
Edward Cree (1):
sfc: Cope with permissions enforcement added to firmware for SR-IOV
Jon Cooper (1):
sfc: Add use of shared RSS contexts.
Shradha Shah (7):
sfc: Own header for nic-specific sriov functions, single instance of
netdev_ops and sriov removed from Falcon code
sfc: Enable VF's via a write to the sysfs file sriov_numvfs
sfc: Use MCDI to set FILTER_OP_IN_TX_DOMAIN
sfc: Prepare to bind the sfc driver to the VF.
sfc: create vports for VFs and assign random MAC addresses
sfc: manually allocate and free vadaptors
sfc: Bind the sfc driver to any available VF's
drivers/net/ethernet/sfc/Makefile | 2 +-
drivers/net/ethernet/sfc/ef10.c | 373 +++++++++++++++++++++++++---
drivers/net/ethernet/sfc/ef10_sriov.c | 430 +++++++++++++++++++++++++++++++++
drivers/net/ethernet/sfc/ef10_sriov.h | 70 ++++++
drivers/net/ethernet/sfc/efx.c | 198 +++++++++------
drivers/net/ethernet/sfc/efx.h | 10 +
drivers/net/ethernet/sfc/ethtool.c | 5 +-
drivers/net/ethernet/sfc/falcon.c | 33 ++-
drivers/net/ethernet/sfc/farch.c | 64 +++--
drivers/net/ethernet/sfc/mcdi.c | 118 ++++++---
drivers/net/ethernet/sfc/mcdi.h | 2 +
drivers/net/ethernet/sfc/mcdi_pcol.h | 23 ++
drivers/net/ethernet/sfc/net_driver.h | 21 +-
drivers/net/ethernet/sfc/nic.h | 133 ++--------
drivers/net/ethernet/sfc/siena.c | 25 +-
drivers/net/ethernet/sfc/siena_sriov.c | 142 ++++++-----
drivers/net/ethernet/sfc/siena_sriov.h | 79 ++++++
drivers/net/ethernet/sfc/sriov.c | 60 +++++
drivers/net/ethernet/sfc/sriov.h | 27 +++
19 files changed, 1455 insertions(+), 360 deletions(-)
create mode 100644 drivers/net/ethernet/sfc/ef10_sriov.c
create mode 100644 drivers/net/ethernet/sfc/ef10_sriov.h
create mode 100644 drivers/net/ethernet/sfc/siena_sriov.h
create mode 100644 drivers/net/ethernet/sfc/sriov.c
create mode 100644 drivers/net/ethernet/sfc/sriov.h
next reply other threads:[~2015-05-05 23:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 23:53 Shradha Shah [this message]
2015-05-05 23:55 ` [PATCH net-next 01/14] sfc: Own header for nic-specific sriov functions, single instance of netdev_ops and sriov removed from Falcon code Shradha Shah
2015-05-05 23:55 ` [PATCH net-next 02/14] sfc: Move and rename efx_vf struct to siena_vf Shradha Shah
2015-05-05 23:55 ` [PATCH net-next 03/14] sfc: Enable VF's via a write to the sysfs file sriov_numvfs Shradha Shah
2015-05-05 23:56 ` [PATCH net-next 04/14] sfc: Use MCDI to set FILTER_OP_IN_TX_DOMAIN Shradha Shah
2015-05-05 23:56 ` [PATCH net-next 05/14] sfc: Record [rt]x_dpcpu_fw_id in EF10 nic_data Shradha Shah
2015-05-05 23:57 ` [PATCH net-next 06/14] sfc: record the PF's vport ID in nic_data Shradha Shah
2015-05-05 23:57 ` [PATCH net-next 07/14] sfc: create VEB vswitch and vport above default firmware setup Shradha Shah
2015-05-05 23:57 ` [PATCH net-next 08/14] sfc: get the PF number and record in nic_data Shradha Shah
2015-05-05 23:58 ` [PATCH net-next 09/14] sfc: Prepare to bind the sfc driver to the VF Shradha Shah
2015-05-05 23:58 ` [PATCH net-next 10/14] sfc: create vports for VFs and assign random MAC addresses Shradha Shah
2015-05-05 23:58 ` [PATCH net-next 11/14] sfc: manually allocate and free vadaptors Shradha Shah
2015-05-05 23:59 ` [PATCH net-next 12/14] sfc: Cope with permissions enforcement added to firmware for SR-IOV Shradha Shah
2015-05-05 23:59 ` [PATCH net-next 13/14] sfc: Add use of shared RSS contexts Shradha Shah
2015-05-06 0:00 ` [PATCH net-next 14/14] sfc: Bind the sfc driver to any available VF's Shradha Shah
2015-05-09 20:18 ` [PATCH net-next 00/14] sfc: Enabling EF10 Vf's, set up vswitching and bind the SFC driver to the VF's 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=554957DF.2010307@solarflare.com \
--to=sshah@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).