From: Yuval Mintz <Yuval.Mintz@qlogic.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: <Ariel.Elior@qlogic.com>, Yuval Mintz <Yuval.Mintz@qlogic.com>
Subject: [PATCH net-next 00/14] qed*: Add SR-IOV support
Date: Mon, 9 May 2016 16:19:09 +0300 [thread overview]
Message-ID: <1462799963-23547-1-git-send-email-Yuval.Mintz@qlogic.com> (raw)
This patch adds SR-IOV support to qed/qede drivers, adding a new PCI
device ID for a VF that is shared between all the various PFs that
support IOV.
This is quite a massive series - the first 7 parts of the series add
the infrastructure of supporting vfs in qed - mainly adding support in a
HW-based vf<->pf channel, as well as diverging all existing configuration
flows based on the pf/vf decision. I.e., while PF-originated requests
head directly to HW/FW, the VF requests first have to traverse to the PF
which will perform the configuration.
The 8th patch is the one that adds the support for the VF device in qede.
The remaining 6 patches each adds some user-based API support related to
VFs that can be used over the PF - forcing mac/vlan, changing speed, etc.
Dave,
Sorry in advance for the length of the series. Most of the bulk here is in
the infrastructure patches that have to go together [or at least, it makes
little sense to try splitting them up].
Please consider applying this to `net-next'.
Thanks,
Yuval
Yuval Mintz (14):
qed: Add CONFIG_QED_SRIOV
qed: Add VF->PF channel infrastructure
qed: Introduce VFs
qed: IOV configure and FLR
qed: IOV l2 functionality
qed: Bulletin and Link
qed: Align TLVs
qede: Add VF support
qed*: Support PVID configuration
qed*: Support forced MAC
qed*: IOV link control
qed*: IOV support spoof-checking
qed*: Support ndo_get_vf_config
qed*: Tx-switching configuration
drivers/net/ethernet/qlogic/Kconfig | 10 +
drivers/net/ethernet/qlogic/qed/Makefile | 1 +
drivers/net/ethernet/qlogic/qed/qed.h | 21 +
drivers/net/ethernet/qlogic/qed/qed_cxt.c | 186 +-
drivers/net/ethernet/qlogic/qed/qed_cxt.h | 3 +
drivers/net/ethernet/qlogic/qed/qed_dev.c | 308 +-
drivers/net/ethernet/qlogic/qed/qed_dev_api.h | 31 +-
drivers/net/ethernet/qlogic/qed/qed_hsi.h | 60 +-
drivers/net/ethernet/qlogic/qed/qed_hw.c | 67 +-
drivers/net/ethernet/qlogic/qed/qed_hw.h | 10 +
drivers/net/ethernet/qlogic/qed/qed_init_ops.c | 4 +
drivers/net/ethernet/qlogic/qed/qed_int.c | 101 +-
drivers/net/ethernet/qlogic/qed/qed_int.h | 16 +
drivers/net/ethernet/qlogic/qed/qed_l2.c | 641 ++--
drivers/net/ethernet/qlogic/qed/qed_l2.h | 239 ++
drivers/net/ethernet/qlogic/qed/qed_main.c | 208 +-
drivers/net/ethernet/qlogic/qed/qed_mcp.c | 155 +-
drivers/net/ethernet/qlogic/qed/qed_mcp.h | 39 +-
drivers/net/ethernet/qlogic/qed/qed_reg_addr.h | 18 +
drivers/net/ethernet/qlogic/qed/qed_sp.h | 6 +-
drivers/net/ethernet/qlogic/qed/qed_sp_commands.c | 13 +-
drivers/net/ethernet/qlogic/qed/qed_spq.c | 19 +-
drivers/net/ethernet/qlogic/qed/qed_sriov.c | 3606 +++++++++++++++++++++
drivers/net/ethernet/qlogic/qed/qed_sriov.h | 386 +++
drivers/net/ethernet/qlogic/qed/qed_vf.c | 1102 +++++++
drivers/net/ethernet/qlogic/qed/qed_vf.h | 990 ++++++
drivers/net/ethernet/qlogic/qede/qede.h | 4 +
drivers/net/ethernet/qlogic/qede/qede_ethtool.c | 43 +-
drivers/net/ethernet/qlogic/qede/qede_main.c | 183 +-
include/linux/qed/common_hsi.h | 62 +
include/linux/qed/qed_eth_if.h | 9 +
include/linux/qed/qed_if.h | 11 +-
include/linux/qed/qed_iov_if.h | 34 +
33 files changed, 8130 insertions(+), 456 deletions(-)
create mode 100644 drivers/net/ethernet/qlogic/qed/qed_l2.h
create mode 100644 drivers/net/ethernet/qlogic/qed/qed_sriov.c
create mode 100644 drivers/net/ethernet/qlogic/qed/qed_sriov.h
create mode 100644 drivers/net/ethernet/qlogic/qed/qed_vf.c
create mode 100644 drivers/net/ethernet/qlogic/qed/qed_vf.h
create mode 100644 include/linux/qed/qed_iov_if.h
--
1.9.3
next reply other threads:[~2016-05-09 13:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 13:19 Yuval Mintz [this message]
2016-05-09 13:19 ` [PATCH net-next 01/14] qed: Add CONFIG_QED_SRIOV Yuval Mintz
2016-05-09 19:14 ` David Miller
2016-05-10 17:16 ` Yuval Mintz
2016-05-10 18:02 ` Alexander Duyck
2016-05-10 18:09 ` David Miller
2016-05-10 18:06 ` David Miller
2016-05-10 18:15 ` Yuval Mintz
2016-05-10 18:27 ` Yuval Mintz
2016-05-10 19:10 ` David Miller
2016-05-09 13:19 ` [PATCH net-next 02/14] qed: Add VF->PF channel infrastructure Yuval Mintz
2016-05-09 13:19 ` [PATCH net-next 03/14] qed: Introduce VFs Yuval Mintz
2016-05-09 13:19 ` [PATCH net-next 04/14] qed: IOV configure and FLR Yuval Mintz
2016-05-09 13:19 ` [PATCH net-next 05/14] qed: IOV l2 functionality Yuval Mintz
2016-05-09 13:19 ` [PATCH net-next 06/14] qed: Bulletin and Link Yuval Mintz
2016-05-09 13:19 ` [PATCH net-next 07/14] qed: Align TLVs Yuval Mintz
2016-05-09 13:19 ` [PATCH net-next 08/14] qede: Add VF support Yuval Mintz
2016-05-09 13:19 ` [PATCH net-next 09/14] qed*: Support PVID configuration Yuval Mintz
2016-05-09 13:19 ` [PATCH net-next 10/14] qed*: Support forced MAC Yuval Mintz
2016-05-09 13:19 ` [PATCH net-next 11/14] qed*: IOV link control Yuval Mintz
2016-05-09 13:19 ` [PATCH net-next 12/14] qed*: IOV support spoof-checking Yuval Mintz
2016-05-09 13:19 ` [PATCH net-next 13/14] qed*: support ndo_get_vf_config Yuval Mintz
2016-05-09 13:19 ` [PATCH net-next 14/14] qed*: Tx-switching configuration Yuval Mintz
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=1462799963-23547-1-git-send-email-Yuval.Mintz@qlogic.com \
--to=yuval.mintz@qlogic.com \
--cc=Ariel.Elior@qlogic.com \
--cc=davem@davemloft.net \
--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).