From: Marcel Apfelbaum <marcel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Liran Liss <liranl@mellanox.com>,
Leon Romanovsky <leonro@mellanox.com>,
Moni Shoua <monis@mellanox.com>, Tzahi Oved <tzahio@mellanox.com>,
Aviad Yehezkel <aviadye@mellanox.com>,
"yuval.shaia@oracle.com" <yuval.shaia@oracle.com>,
qemu-devel <qemu-devel@nongnu.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
virtio-dev@lists.oasis-open.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] Virtual RDMA device
Date: Mon, 7 Aug 2017 22:53:42 +0300 [thread overview]
Message-ID: <db6cd719-d56c-05d0-1453-4f7b0b374ad9@redhat.com> (raw)
In-Reply-To: <20170801003938-mutt-send-email-mst@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2212 bytes --]
On 01/08/2017 0:52, Michael S. Tsirkin wrote:
> On Mon, Jul 31, 2017 at 10:10:15PM +0300, Marcel Apfelbaum wrote:
[...]
>> This seems to be the mail thread with most CCs.
>
Hi Michael,
> Please copy the upstream lists. virtio-dev, virtualization and
> qemu-devel for starters. I'd say linux-rdma as well.
>
Sure, adding all the mentioned lists.
To recap:
Yuval and I succeeded to implement a QEMU pvrdma device that works
(with some limitations) with VMware's Linux driver.
The git can be found at:
https://github.com/yuvalshaia/qemu/tree/pvrdma.master.ibverbs
The QEMU RFC at:
https://patchwork.kernel.org/patch/9653893/
While we do plan to merge it to QEMU, as a next step it seems
to be a consensus that virtio should be used to implement guest<->host
communication; since the project is not small, we need a plan.
We will do our best to attend the Micro RDMA conference:
-
https://www.linuxplumbersconf.org/2017/rdma-microconference-accepted-into-the-linux-plumbers-conference/
The attached presentation draft is intended to be a starting point
for a discussion on how to continue the project.
>> I attached a presentation
>> draft with *current* implementation of the pvrdma
>> device.(please excuse my presentation skills).
>>
>> It is supposed to be a starting point for discussing
>> a virtio-rdma device and for a presentation at
>> the RDMA Micro-conference.
>>
>> Please feel free to review/add and point to
>> what important things have I missed and how
>> we can continue.
>
> I'd suggest ignoring migration initially, just get
> rdma with memory overcommit working. For that:
> - come up with a timeline
> - decide who works on each of 3 things
> 1. extend libibverbs
> 2. layer virtio in qemu on top
> 3. write guest driver
>
>
>>
>> I want to mention there is another discussion on this matter:
>> https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg06012.html
>
> That simply lists what is missing in libibverbs to be able to implement
> a PV RDMA device with memory overcommit and migration on top.
>
>> We should converge somehow.
>> Once Yuval returns from his vacation we will send a v2.
>>
>> Thanks,
>> Marcel
>>
>>>
>
[...]
Thanks,
Marcel
[-- Attachment #2: pvrdma.odp --]
[-- Type: application/vnd.oasis.opendocument.presentation, Size: 17633 bytes --]
parent reply other threads:[~2017-08-07 19:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170801003938-mutt-send-email-mst@kernel.org>]
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=db6cd719-d56c-05d0-1453-4f7b0b374ad9@redhat.com \
--to=marcel@redhat.com \
--cc=aviadye@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=liranl@mellanox.com \
--cc=monis@mellanox.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tzahio@mellanox.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=yuval.shaia@oracle.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).