All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Bairen <byron-DzDj5FMp9MpyDzI6CaY1VQ@public.gmane.org>
To: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Loopback with RXE?
Date: Sat, 17 Feb 2018 13:03:05 +0000	[thread overview]
Message-ID: <F17D72E0-CBBE-4315-A576-91EA43EAB388@rbird.tech> (raw)
In-Reply-To: <20180214192559.GC8800@yuvallap>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 3553 bytes --]

Hi,

> On 15 Feb 2018, at 03:25, Yuval Shaia <yuval.shaia@oracle.com> wrote:
> 
> 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?

The rdma_client and rdma_server do work with `end 0`. 

The ib_write_bw seems to hang. If I kill the server side, the client does not respond. If I kill the client side, it shows the following log:

$ ib_write_bw

************************************
* Waiting for client to connect... *
************************************
---------------------------------------------------------------------------------------
                    RDMA_Write BW Test
 Dual-port       : OFF		Device         : rxe0
 Number of qps   : 1		Transport type : IB
 Connection type : RC		Using SRQ      : OFF
 CQ Moderation   : 100
 Mtu             : 1024[B]
 Link type       : Ethernet
 GID index       : 1
 Max inline data : 0[B]
 rdma_cm QPs	 : OFF
 Data ex. method : Ethernet
---------------------------------------------------------------------------------------
 local address: LID 0000 QPN 0x0014 PSN 0x3787ca RKey 0x00052c VAddr 0x007f3dd4c42000
 GID: 00:00:00:00:00:00:00:00:00:00:255:255:159:65:13:34
 remote address: LID 0000 QPN 0x0015 PSN 0x5c8ba9 RKey 0x000658 VAddr 0x007f30e74b3000
 GID: 00:00:00:00:00:00:00:00:00:00:255:255:159:65:13:34
---------------------------------------------------------------------------------------
 #bytes     #iterations    BW peak[MB/sec]    BW average[MB/sec]   MsgRate[Mpps]
ethernet_read_keys: Couldn't read remote address
 Unable to read to socket/rdam_cm
 Failed to exchange data between server and clients

 #bytes     #iterations    BW peak[MB/sec]    BW average[MB/sec]   MsgRate[Mpps]
ethernet_read_keys: Couldn't read remote address
 Unable to read to socket/rdam_cm
 Failed to exchange data between server and clients

My RXE config:

$ sudo rxe_cfg start
  Name     Link  Driver      Speed  NMTU  IPv4_addr  RDEV  RMTU
  docker0  no    bridge
  eth0     yes   virtio_net                          rxe0  1024  (3)
  eth1     yes   virtio_net                          rxe1  1024  (3)

dmesg:

[14441.336707] rdma_rxe: loaded
[14441.375108] Loading iSCSI transport class v2.0-870.
[14441.380930] rdma_rxe: set rxe0 active
[14441.381824] rdma_rxe: added rxe0 to eth0
[14441.389567] iscsi: registered transport (iser)
[14441.403595] RPC: Registered named UNIX socket transport module.
[14441.404618] RPC: Registered udp transport module.
[14441.405390] RPC: Registered tcp transport module.
[14441.406057] RPC: Registered tcp NFSv4.1 backchannel transport module.
[14441.415816] RPC: Registered rdma transport module.
[14441.416689] RPC: Registered rdma backchannel transport module.
[14441.419979] rdma_rxe: set rxe1 active
[14441.420657] rdma_rxe: added rxe1 to eth1
[14470.422836] detected loopback device
[14484.278022] rdma_rxe: qp#18 moved to error state

> 
>> 
>> I’d like to know if rxe loopback is known to be broken, and how to fix it.
>> 
>> Best,
>> Bairen Yi

Bairen Yi

N‹§²æìr¸›yúèšØb²X¬¶Ç§vØ^–)Þº{.nÇ+‰·¥Š{±­ÙšŠ{ayº\x1dʇڙë,j\a­¢f£¢·hš‹»öì\x17/oSc¾™Ú³9˜uÀ¦æå‰È&jw¨®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿïêäz¹Þ–Šàþf£¢·hšˆ§~ˆmš

  reply	other threads:[~2018-02-17 13:03 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
2018-02-17 13:03     ` Yi Bairen [this message]
     [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=F17D72E0-CBBE-4315-A576-91EA43EAB388@rbird.tech \
    --to=byron-dzdj5fmp9mpydzi6cay1vq@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@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 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.