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,
netdev@vger.kernel.org, dan.daly@intel.com,
cunming.liang@intel.com, tiwei.bie@intel.com,
jason.zeng@intel.com, zhiyuan.lv@intel.com,
Zhu Lingshan <lingshan.zhu@intel.com>
Subject: [RFC 0/2] Intel IFC VF driver for vdpa
Date: Wed, 16 Oct 2019 09:03:16 +0800 [thread overview]
Message-ID: <20191016010318.3199-1-lingshan.zhu@intel.com> (raw)
Hi all:
This series intends to introduce Intel IFC VF NIC driver for Vhost
Data Plane Acceleration.
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 vhost_mdev https://lkml.org/lkml/2019/9/26/15
This is a first RFC try, please help review.
Thanks!
BR
Zhu Lingshan
Zhu Lingshan (2):
vhost: IFC VF hardware operation layer
vhost: IFC VF vdpa layer
drivers/vhost/ifcvf/ifcvf_base.c | 390 ++++++++++++++++++++++++++++
drivers/vhost/ifcvf/ifcvf_base.h | 137 ++++++++++
drivers/vhost/ifcvf/ifcvf_main.c | 541 +++++++++++++++++++++++++++++++++++++++
3 files changed, 1068 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
--
2.16.4
next reply other threads:[~2019-10-16 1:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 1:03 Zhu Lingshan [this message]
2019-10-16 1:03 ` [RFC 1/2] vhost: IFC VF hardware operation layer Zhu Lingshan
2019-10-16 2:04 ` Stephen Hemminger
2019-10-16 2:06 ` Stephen Hemminger
2019-10-29 7:36 ` Zhu, Lingshan
2019-10-16 1:03 ` [RFC 2/2] vhost: IFC VF vdpa layer Zhu Lingshan
2019-10-16 9:53 ` Simon Horman
2019-10-21 8:48 ` Zhu, Lingshan
2019-10-16 1:10 [RFC 0/2] Intel IFC VF driver for vdpa Zhu Lingshan
2019-10-16 1:30 Zhu Lingshan
2019-10-16 1:36 ` Zhu Lingshan
2019-10-16 8:26 ` Jason Wang
2019-10-21 7:10 ` 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=20191016010318.3199-1-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=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 \
--cc=zhiyuan.lv@intel.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).