qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* Re: [Qemu-devel] Virtual RDMA device
       [not found]           ` <20170801003938-mutt-send-email-mst@kernel.org>
@ 2017-08-07 19:53             ` Marcel Apfelbaum
  0 siblings, 0 replies; only message in thread
From: Marcel Apfelbaum @ 2017-08-07 19:53 UTC (permalink / raw)
  To: Michael S. Tsirkin
  Cc: Liran Liss, Leon Romanovsky, Moni Shoua, Tzahi Oved,
	Aviad Yehezkel, yuval.shaia@oracle.com, qemu-devel, linux-rdma,
	virtio-dev, virtualization

[-- 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 --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2017-08-07 19:54 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <DB5PR0501MB1928246450227EDF80AE0E50B0AF0@DB5PR0501MB1928.eurprd05.prod.outlook.com>
     [not found] ` <DB6PR0501MB2037EE71981AC82BDC42D19AD3AF0@DB6PR0501MB2037.eurprd05.prod.outlook.com>
     [not found]   ` <bf8b870b-a415-df56-7533-cb93803169fa@redhat.com>
     [not found]     ` <DB5PR0501MB19280F11B85DC0C9D51AF567B0AC0@DB5PR0501MB1928.eurprd05.prod.outlook.com>
     [not found]       ` <HE1PR0501MB2812B5FBFB7B4470BB7FA1CEB1A30@HE1PR0501MB2812.eurprd05.prod.outlook.com>
     [not found]         ` <1a9c127c-00eb-fe81-3bc3-09bbed4574d9@redhat.com>
     [not found]           ` <20170801003938-mutt-send-email-mst@kernel.org>
2017-08-07 19:53             ` [Qemu-devel] Virtual RDMA device Marcel Apfelbaum

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).