From: Leon Romanovsky <leon@kernel.org>
To: Yuval Shaia <yuval.shaia@oracle.com>
Cc: RDMA mailing list <linux-rdma@vger.kernel.org>,
linux-netdev <netdev@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Jason Gunthorpe <jgg@ziepe.ca>,
Doug Ledford <dledford@redhat.com>
Subject: Re: CFP: 4th RDMA Mini-Summit at LPC 2019
Date: Wed, 15 May 2019 19:36:26 +0300 [thread overview]
Message-ID: <20190515163626.GO5225@mtr-leonro.mtl.com> (raw)
In-Reply-To: <20190515153050.GB2356@lap1>
On Wed, May 15, 2019 at 06:30:51PM +0300, Yuval Shaia wrote:
> On Tue, May 14, 2019 at 03:23:21PM +0300, Leon Romanovsky wrote:
> > This is a call for proposals for the 4th RDMA mini-summit at the Linux
> > Plumbers Conference in Lisbon, Portugal, which will be happening on
> > September 9-11h, 2019.
> >
> > We are looking for topics with focus on active audience discussions
> > and problem solving. The preferable topic is up to 30 minutes with
> > 3-5 slides maximum.
>
> Abstract: Expand the virtio portfolio with RDMA
>
> Description:
> Data center backends use more and more RDMA or RoCE devices and more and
> more software runs in virtualized environment.
> There is a need for a standard to enable RDMA/RoCE on Virtual Machines.
> Virtio is the optimal solution since is the de-facto para-virtualizaton
> technology and also because the Virtio specification allows Hardware
> Vendors to support Virtio protocol natively in order to achieve bare metal
> performance.
> This talk addresses challenges in defining the RDMA/RoCE Virtio
> Specification and a look forward on possible implementation techniques.
Yuval,
Who is going to implement it?
Thanks
>
> >
> > This year, the LPC will include netdev track too and it is
> > collocated with Kernel Summit, such timing makes an excellent
> > opportunity to drive cross-tree solutions.
> >
> > BTW, RDMA is not accepted yet as a track in LPC, but let's think
> > positive and start collect topics.
> >
> > Thanks
next prev parent reply other threads:[~2019-05-15 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 12:23 Leon Romanovsky
2019-05-15 15:30 ` Yuval Shaia
2019-05-15 16:36 ` Leon Romanovsky [this message]
2019-05-15 18:15 ` Yuval Shaia
2019-05-16 7:08 ` Kamal Heib
2019-05-16 7:41 ` Leon Romanovsky
2019-05-28 11:40 ` Leon Romanovsky
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=20190515163626.GO5225@mtr-leonro.mtl.com \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.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