From: Zhu Lingshan <lingshan.zhu@intel.com>
To: mst@redhat.com, jasowang@redhat.com, alex.williamson@redhat.com
Cc: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
netdev@vger.kernel.org, dan.daly@intel.com,
cunming.liang@intel.com, tiwei.bie@intel.com,
jason.zeng@intel.com, Zhu Lingshan <lingshan.zhu@intel.com>
Subject: [PATCH 0/2] Intel IFC VF driver for VDPA
Date: Tue, 5 Nov 2019 17:37:38 +0800 [thread overview]
Message-ID: <1572946660-26265-1-git-send-email-lingshan.zhu@intel.com> (raw)
Hi all:
This series intends to introduce Intel IFC VF NIC driver for Vhost
Data Plane Acceleration(VDPA).
Here comes two main parts, one is ifcvf_base layer, which handles
hardware operations. The other is ifcvf_main layer handles VF
initialization, configuration and removal, which depends on
and complys to:
virtio_mdev https://lkml.org/lkml/2019/10/30/62
vhost_mdev https://lkml.org/lkml/2019/10/31/440
This patchset passed netperf tests.
This is RFC V2, plese help review.
Changes from V1:
using le32_to_cpu() to convert PCI capabilities.
some set /get operations will sync with the hardware, eg get_status
and get_generation.
remove feature bit VHOST_F_LOG_ALL, add VIRTIO_F_ORDERED_PLATFORM
add get/set_config functions.
split mdev type group into mdev_type_group_virtio and mdev_type_group_vhost
add ifcvf_mdev_get_mdev_features()
coding stype changes.
Zhu Lingshan (2):
IFC hardware operation layer
IFC VDPA layer
drivers/vhost/ifcvf/ifcvf_base.c | 344 ++++++++++++++++++++++
drivers/vhost/ifcvf/ifcvf_base.h | 132 +++++++++
drivers/vhost/ifcvf/ifcvf_main.c | 605 +++++++++++++++++++++++++++++++++++++++
3 files changed, 1081 insertions(+)
create mode 100644 drivers/vhost/ifcvf/ifcvf_base.c
create mode 100644 drivers/vhost/ifcvf/ifcvf_base.h
create mode 100644 drivers/vhost/ifcvf/ifcvf_main.c
--
1.8.3.1
next reply other threads:[~2019-11-05 9:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 9:37 Zhu Lingshan [this message]
2019-11-05 9:37 ` [PATCH 1/2] IFC hardware operation layer Zhu Lingshan
2019-11-05 11:29 ` Michael S. Tsirkin
2019-11-08 11:55 ` Zhu Lingshan
2019-11-05 12:45 ` Michael S. Tsirkin
2019-11-05 12:47 ` Jason Wang
2019-11-08 8:04 ` Zhu Lingshan
2019-11-06 10:09 ` Jason Wang
2019-11-08 12:24 ` Zhu Lingshan
2019-11-08 12:57 ` Michael S. Tsirkin
2019-11-08 13:07 ` Zhu Lingshan
2019-11-09 20:07 ` Mark D Rustad
2019-11-05 9:37 ` [PATCH 2/2] IFC VDPA layer Zhu Lingshan
2019-11-06 10:39 ` Jason Wang
2019-11-08 12:46 ` Zhu Lingshan
2019-11-12 8:54 ` Zhu Lingshan
2019-11-09 19:56 ` Mark D Rustad
2019-11-12 8:40 ` Zhu Lingshan
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=1572946660-26265-1-git-send-email-lingshan.zhu@intel.com \
--to=lingshan.zhu@intel.com \
--cc=alex.williamson@redhat.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=jason.zeng@intel.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=tiwei.bie@intel.com \
--cc=virtualization@lists.linux-foundation.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