linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: wangqi <3100102071@zju.edu.cn>, linux-rdma@vger.kernel.org
Subject: Re: [question]can hard roce and soft roce communicate with each other?
Date: Wed, 27 Nov 2019 13:10:08 +0200	[thread overview]
Message-ID: <20191127111008.GC10331@unreal> (raw)
In-Reply-To: <4433c97d-218a-294e-3c03-214e0ef1379f@acm.org>

On Tue, Nov 26, 2019 at 04:53:14PM -0800, Bart Van Assche wrote:
> On 11/21/19 11:19 PM, wangqi wrote:
> >      Do you know how to make soft-roce (on server) can send message
> > to the hard-roce (like Mellanox cx4 card) on a client? We tried rdma-core
> > 25.0 and 26.0. The rdma-core can support both soft-roce and hard-roce.
> >
> > But it seems that the soft-roce (server) and hard-roce (client) can not
> > communicate via "ib_send_bw", "ib_read_bw" and so on, but can
> > communicate via "rping".
> >
> >      Do you ever try to use soft-roce and hard-roce together?
> > Do they work well? I really wonder why they can not communicate with
> > each other. Best wishes,
>
> I think this should be possible. The diagram on the following web page shows
> a RoCE NIC and softROCE connected to each other:
>
> http://www.roceinitiative.org/software-based-roce-a-new-way-to-experience-rdma/

It should work, but it didn't work for me now :)

Thanks

>
> Bart.

  reply	other threads:[~2019-11-27 11:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22  7:19 [question]can hard roce and soft roce communicate with each other? wangqi
2019-11-27  0:53 ` Bart Van Assche
2019-11-27 11:10   ` Leon Romanovsky [this message]
2019-11-27 14:24     ` Steve Wise
2019-12-03  0:56       ` Bart Van Assche
2019-12-03  1:57         ` Steve Wise
2019-12-03 21:48           ` Steve Wise

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=20191127111008.GC10331@unreal \
    --to=leon@kernel.org \
    --cc=3100102071@zju.edu.cn \
    --cc=bvanassche@acm.org \
    --cc=linux-rdma@vger.kernel.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).