All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Junji Wei <weijunji@bytedance.com>, virtio-dev@lists.oasis-open.org
Cc: weijunji@bytedance.com, dledford@redhat.com, jgg@ziepe.ca,
	mst@redhat.com, jasowang@redhat.com, yuval.shaia.ml@gmail.com,
	marcel.apfelbaum@gmail.com, hare@suse.de,
	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: Wed, 22 Sep 2021 13:28:12 +0200	[thread overview]
Message-ID: <87czp0g88j.fsf@redhat.com> (raw)
In-Reply-To: <20210903080303.39915-1-weijunji@bytedance.com>

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


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


  parent reply	other threads:[~2021-09-22 11:28 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 ` Cornelia Huck [this message]
2021-09-23  3:00   ` Junji Wei
2021-09-24 13:50     ` [virtio-dev] " Cornelia Huck
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=87czp0g88j.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.