From: Jason Wang <jasowang@redhat.com>
To: Zhu Lingshan <lingshan.zhu@linux.intel.com>,
Zhu Lingshan <lingshan.zhu@intel.com>,
mst@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, zhiyuan.lv@intel.com
Subject: Re: [RFC 0/2] Intel IFC VF driver for vdpa
Date: Wed, 16 Oct 2019 16:26:10 +0800 [thread overview]
Message-ID: <47befa11-c943-42f7-85c9-01b12f497182@redhat.com> (raw)
In-Reply-To: <37503c7d-c07d-e584-0b6f-3733d2ad1dc7@linux.intel.com>
On 2019/10/16 上午9:36, Zhu Lingshan wrote:
> failed to send to kvm list, resend, sorry for the inconvenience.
>
> THanks,
> BR
> Zhu Lingshan
>
> On 10/16/2019 9:30 AM, Zhu Lingshan wrote:
>> 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.
It would be helpful if yon can describe which kinds of test that has
been done for this series.
Thanks
>> 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
>>
next prev parent reply other threads:[~2019-10-16 8:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 1:30 [RFC 0/2] Intel IFC VF driver for vdpa Zhu Lingshan
2019-10-16 1:30 ` [RFC 1/2] vhost: IFC VF hardware operation layer Zhu Lingshan
2019-10-16 8:40 ` Jason Wang
2019-10-21 10:00 ` Zhu, Lingshan
2019-10-21 10:35 ` Jason Wang
2019-10-16 8:45 ` Jason Wang
2019-10-21 9:57 ` Zhu, Lingshan
2019-10-21 10:21 ` Jason Wang
2019-10-16 1:30 ` [RFC 2/2] vhost: IFC VF vdpa layer Zhu Lingshan
2019-10-16 10:19 ` Jason Wang
2019-10-18 6:36 ` Zhu, Lingshan
2019-10-21 9:53 ` Zhu, Lingshan
2019-10-21 10:19 ` Jason Wang
2019-10-22 6:53 ` Zhu Lingshan
2019-10-22 13:05 ` Jason Wang
2019-10-23 6:19 ` Zhu, Lingshan
2019-10-23 6:39 ` Jason Wang
2019-10-23 9:24 ` Zhu, Lingshan
2019-10-23 9:58 ` Jason Wang
2019-10-16 1:36 ` [RFC 0/2] Intel IFC VF driver for vdpa Zhu Lingshan
2019-10-16 8:26 ` Jason Wang [this message]
2019-10-21 7:10 ` Zhu, Lingshan
-- strict thread matches above, loose matches on Subject: below --
2019-10-16 1:10 Zhu Lingshan
2019-10-16 1:03 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=47befa11-c943-42f7-85c9-01b12f497182@redhat.com \
--to=jasowang@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=jason.zeng@intel.com \
--cc=kvm@vger.kernel.org \
--cc=lingshan.zhu@intel.com \
--cc=lingshan.zhu@linux.intel.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).