qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yuval Shaia <yuval.shaia@oracle.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
	Doug Ledford <dledford@redhat.com>,
	qemu-devel@nongnu.org, linux-rdma@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH RFC] hw/pvrdma: Proposal of a new pvrdma device
Date: Thu, 6 Apr 2017 22:45:54 +0300	[thread overview]
Message-ID: <20170406194552.GB2170@yuval-lap> (raw)
In-Reply-To: <20170404173349.GY20443@mtr-leonro.local>

On Tue, Apr 04, 2017 at 08:33:49PM +0300, Leon Romanovsky wrote:
> 
> I'm not going to repeat Jason's answer, I'm completely agree with him.
> 
> Just add my 2 cents. You didn't answer on my question about other possible
> implementations. It can be SoftRoCE loopback optimizations, special ULP,
> RDMA transport, virtual driver with multiple VFs and single PF.

Please see my response to Jason's comments - eventually, when a support for
VM to external host communication will be added - kdbr will become ULP as
well.

Marcel & Yuval

> 
> >

  reply	other threads:[~2017-04-06 19:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 11:12 [Qemu-devel] [PATCH RFC] hw/pvrdma: Proposal of a new pvrdma device Marcel Apfelbaum
2017-03-30 14:13 ` Leon Romanovsky
2017-03-30 20:28   ` Doug Ledford
2017-03-30 23:38     ` Adit Ranadive
2017-03-31 15:50       ` Marcel Apfelbaum
2017-03-31 15:45     ` Marcel Apfelbaum
2017-04-03  6:23       ` Leon Romanovsky
2017-04-04 13:38         ` Marcel Apfelbaum
2017-04-04 16:01           ` Jason Gunthorpe
2017-04-06 19:42             ` Yuval Shaia
2017-04-06 20:38               ` Jason Gunthorpe
2017-04-04 17:33           ` Leon Romanovsky
2017-04-06 19:45             ` Yuval Shaia [this message]
2017-04-06 20:54               ` Jason Gunthorpe
2017-04-03  6:27     ` 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=20170406194552.GB2170@yuval-lap \
    --to=yuval.shaia@oracle.com \
    --cc=dledford@redhat.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=marcel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).