From: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Yi Bairen <byron-DzDj5FMp9MpyDzI6CaY1VQ@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Loopback with RXE?
Date: Wed, 14 Feb 2018 21:25:59 +0200 [thread overview]
Message-ID: <20180214192559.GC8800@yuvallap> (raw)
In-Reply-To: <2145E340-3297-4ED2-BEC9-09E4CD582D24-DzDj5FMp9MpyDzI6CaY1VQ@public.gmane.org>
On Wed, Feb 14, 2018 at 05:13:07PM +0000, Yi Bairen wrote:
> Hi folks,
>
> Seems I can’t get a Linux 4.9 (Debian 9.3) VM working with single box SoftRoCE loopback. I installed rdma-core 16. The rdma_client & rdma_server in the same box seems working. However, when I use ib_write_bw in the same box, the QPs can’t be connected through the same rxe device.
If the QPs connection is problematic then how come rdma_* is working?
>
> I’d like to know if rxe loopback is known to be broken, and how to fix it.
>
> Best,
> Bairen Yi
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-02-14 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 17:13 Loopback with RXE? Yi Bairen
[not found] ` <2145E340-3297-4ED2-BEC9-09E4CD582D24-DzDj5FMp9MpyDzI6CaY1VQ@public.gmane.org>
2018-02-14 17:48 ` Majd Dibbiny
2018-02-14 19:25 ` Yuval Shaia [this message]
2018-02-17 13:03 ` Yi Bairen
[not found] ` <F17D72E0-CBBE-4315-A576-91EA43EAB388-DzDj5FMp9MpyDzI6CaY1VQ@public.gmane.org>
2018-02-17 21:23 ` Majd Dibbiny
[not found] ` <37E490E3-75A6-4C2B-B82D-6ED11031EA09-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-18 10:47 ` Bairen Yi
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=20180214192559.GC8800@yuvallap \
--to=yuval.shaia-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=byron-DzDj5FMp9MpyDzI6CaY1VQ@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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