From: Leon Romanovsky <leon@kernel.org>
To: Junji Wei <weijunji@bytedance.com>
Cc: "Jason Wang" <jasowang@redhat.com>,
"Doug Ledford" <dledford@redhat.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>, mst <mst@redhat.com>,
yuval.shaia.ml@gmail.com,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Hannes Reinecke" <hare@suse.de>,
Virtio-Dev <virtio-dev@lists.oasis-open.org>,
"Yongji Xie" <xieyongji@bytedance.com>,
柴稳 <chaiwen.cc@bytedance.com>,
"Xiongchun Duan" <duanxiongchun@bytedance.com>,
zhoujielong@bytedance.com, zhangqianyu.sys@bytedance.com,
"RDMA mailing list" <linux-rdma@vger.kernel.org>
Subject: Re: [virtio-dev] Re: [RFC] Virtio RDMA
Date: Wed, 16 Feb 2022 11:48:47 +0200 [thread overview]
Message-ID: <YgzIfyx7WyGb39mV@unreal> (raw)
In-Reply-To: <2818E401-AA08-42DB-90C0-75B199ECE47E@bytedance.com>
On Wed, Feb 16, 2022 at 04:00:53PM +0800, Junji Wei wrote:
<...>
> >
> > What is the use case for this virtio-rdma? Especially in context of RXE.
>
> Hmm... yes, we didn’t find one. In passthrough case we can use RXE directly.
It doesn't sound like a good sales pitch.
>
> Thanks.
next prev parent reply other threads:[~2022-02-16 9:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 8:13 [RFC] Virtio RDMA Junji Wei
2022-02-15 8:44 ` Jason Wang
2022-02-15 10:02 ` Junji Wei
2022-02-16 5:54 ` Jason Wang
2022-02-16 6:50 ` [virtio-dev] " Junji Wei
2022-02-16 6:58 ` Jason Wang
2022-02-16 7:13 ` Junji Wei
2022-02-16 7:26 ` Leon Romanovsky
2022-02-16 8:00 ` Junji Wei
2022-02-16 9:48 ` Leon Romanovsky [this message]
2022-02-16 10:03 ` Junji Wei
2022-02-16 12:06 ` Leon Romanovsky
2022-02-16 14:08 ` Yongji Xie
2022-02-16 14:21 ` Hannes Reinecke
2022-02-17 3:38 ` Yongji Xie
2022-02-16 15:40 ` Doug Ledford
2022-02-17 3:24 ` Yongji Xie
2022-02-17 7:02 ` Jason Wang
2022-02-17 7:34 ` [External] " Junji Wei
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=YgzIfyx7WyGb39mV@unreal \
--to=leon@kernel.org \
--cc=chaiwen.cc@bytedance.com \
--cc=cohuck@redhat.com \
--cc=dledford@redhat.com \
--cc=duanxiongchun@bytedance.com \
--cc=hare@suse.de \
--cc=jasowang@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--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 \
--cc=zhangqianyu.sys@bytedance.com \
--cc=zhoujielong@bytedance.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.