From: Manish Chopra <manishc@marvell.com>
To: <jerinjacobk@gmail.com>, <jerinj@marvell.com>, <ferruh.yigit@intel.com>
Cc: <dev@dpdk.org>, <irusskikh@marvell.com>, <rmody@marvell.com>,
<GR-Everest-DPDK-Dev@marvell.com>
Subject: [dpdk-dev] [PATCH 0/6] qede: SR-IOV PF driver support
Date: Tue, 9 Jun 2020 12:42:01 -0700 [thread overview]
Message-ID: <20200609194207.24328-1-manishc@marvell.com> (raw)
Hi,
This series adds SR-IOV PF pmd driver support to have VF pmd
driver work over PF pmd driver instances in order to run the
adapter completely under DPDK environment for one of the use
cases like ovs-dpdk.
This is very initial bring-up with following testing covered -
* Enable/Disable SR-IOV VFs through igb_uio sysfs hook.
* Load VFs, run fastpath, teardown VFs in hypervisor and guest VM.
* VF FLR flow (in case of VF PCI passthrough to the guest VM)
* Bulletin mechanism tested to communicate link changes to the VFs.
Note that this series is only intended for upcoming DPDK release (20.08)
Please consider applying this series to dpdk-next-net-mrvl.git
Thanks,
Manish
Manish Chopra (6):
net/qede: define PCI config space specific osals
net/qede: configure VFs on hardware
net/qede: add infrastructure support for VF load
net/qede: initialize VF MAC and link
net/qede: add VF FLR support
doc/guides: update qede features list
doc/guides/nics/features/qede.ini | 1 +
doc/guides/nics/qede.rst | 2 +-
drivers/net/qede/Makefile | 1 +
drivers/net/qede/base/bcm_osal.c | 71 +++++++++
drivers/net/qede/base/bcm_osal.h | 30 +++-
drivers/net/qede/base/ecore.h | 27 ++++
drivers/net/qede/base/ecore_iov_api.h | 3 +
drivers/net/qede/meson.build | 1 +
drivers/net/qede/qede_ethdev.c | 37 ++++-
drivers/net/qede/qede_ethdev.h | 1 +
drivers/net/qede/qede_if.h | 1 +
drivers/net/qede/qede_main.c | 13 +-
drivers/net/qede/qede_sriov.c | 219 ++++++++++++++++++++++++++
drivers/net/qede/qede_sriov.h | 22 +++
14 files changed, 417 insertions(+), 12 deletions(-)
create mode 100644 drivers/net/qede/qede_sriov.c
create mode 100644 drivers/net/qede/qede_sriov.h
--
2.17.1
next reply other threads:[~2020-06-09 19:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 19:42 Manish Chopra [this message]
2020-06-09 19:42 ` [dpdk-dev] [PATCH 1/6] net/qede: define PCI config space specific osals Manish Chopra
2020-06-26 4:53 ` Jerin Jacob
2020-07-09 15:05 ` [dpdk-dev] [EXT] " Manish Chopra
2020-07-09 16:11 ` Jerin Jacob
2020-07-09 22:28 ` Manish Chopra
2020-07-10 5:03 ` Jerin Jacob
2020-06-09 19:42 ` [dpdk-dev] [PATCH 2/6] net/qede: configure VFs on hardware Manish Chopra
2020-06-09 19:42 ` [dpdk-dev] [PATCH 3/6] net/qede: add infrastructure support for VF load Manish Chopra
2020-06-09 19:42 ` [dpdk-dev] [PATCH 4/6] net/qede: initialize VF MAC and link Manish Chopra
2020-06-09 19:42 ` [dpdk-dev] [PATCH 5/6] net/qede: add VF FLR support Manish Chopra
2020-06-09 19:42 ` [dpdk-dev] [PATCH 6/6] doc/guides: update qede features list Manish Chopra
2020-06-26 4:55 ` Jerin Jacob
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=20200609194207.24328-1-manishc@marvell.com \
--to=manishc@marvell.com \
--cc=GR-Everest-DPDK-Dev@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=irusskikh@marvell.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=rmody@marvell.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).