Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Junji Wei <weijunji@bytedance.com>
Cc: virtio-dev@lists.oasis-open.org,
	"Doug Ledford" <dledford@redhat.com>,
	"Jason Gunthorpe" <jgg@ziepe.ca>, mst <mst@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>,
	yuval.shaia.ml@gmail.com, marcel.apfelbaum@gmail.com,
	"Hannes Reinecke" <hare@suse.de>,
	"Yongji Xie" <xieyongji@bytedance.com>,
	柴稳 <chaiwen.cc@bytedance.com>,
	dingtao.darren@bytedance.com, duanxiongchun@bytedance.com
Subject: [virtio-dev] Re: [PATCH] Reserve device id for RDMA device
Date: Fri, 24 Sep 2021 15:50:07 +0200	[thread overview]
Message-ID: <87czoydqwg.fsf@redhat.com> (raw)
In-Reply-To: <291795BE-C269-42C9-84E8-74D5CDE59704@bytedance.com>

On Thu, Sep 23 2021, Junji Wei <weijunji@bytedance.com> wrote:

>> On Sep 22, 2021, at 7:28 PM, Cornelia Huck <cohuck@redhat.com> wrote:
>> 
>> On Fri, Sep 03 2021, Junji Wei <weijunji@bytedance.com> wrote:
>> 
>>> Use device ID 42
>>> 
>>> Signed-off-by: Junji Wei <weijunji@bytedance.com>
>>> ---
>>> content.tex | 2 ++
>>> 1 file changed, 2 insertions(+)
>>> 
>>> diff --git a/content.tex b/content.tex
>>> index 3aeb4a4..b57c997 100644
>>> --- a/content.tex
>>> +++ b/content.tex
>>> @@ -2878,6 +2878,8 @@ \chapter{Device Types}\label{sec:Device Types}
>>> \hline
>>> 41         &   GPIO device \\
>>> \hline
>>> +42         &   RDMA device \\
>>> +\hline
>>> \end{tabular}
>>> 
>>> Some of the devices above are unspecified by this document,
>> 
>> Do we have an answer to the issues raised with the QEMU patches? IOW, is
>
> Yes.
>
>> it reasonable to expect that we can actually implement a usuable RDMA
>> device? While device IDs are generally cheap, it would be good not to
>> have too many dead entries.
>
> I think we can implement an usable RDMA device through uRDMA (a
> software implementation of the RoCEv2 protocol in QEMU with VFIO
> or DPDK).

If nobody disagrees, we can start a vote.

One last question: there were two patches, this one and the one linked
in the issue... I think they are the same, right? (I do not trust myself
on Friday afternoons.)


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2021-09-24 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03  8:03 [PATCH] Reserve device id for RDMA device Junji Wei
2021-09-03  8:32 ` Michael S. Tsirkin
2021-09-22 11:28 ` [virtio-dev] " Cornelia Huck
2021-09-23  3:00   ` Junji Wei
2021-09-24 13:50     ` Cornelia Huck [this message]
2021-09-24 14:29       ` [External] " 魏俊吉

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=87czoydqwg.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=chaiwen.cc@bytedance.com \
    --cc=dingtao.darren@bytedance.com \
    --cc=dledford@redhat.com \
    --cc=duanxiongchun@bytedance.com \
    --cc=hare@suse.de \
    --cc=jasowang@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=weijunji@bytedance.com \
    --cc=xieyongji@bytedance.com \
    --cc=yuval.shaia.ml@gmail.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