public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Marcin Mielniczuk <marcin@golem.network>
Cc: Leon Romanovsky <leon@kernel.org>,
	Krishnamraju Eraparaju <krishna2@chelsio.com>,
	linux-rdma@vger.kernel.org
Subject: Re: Setting up siw devices
Date: Fri, 23 Aug 2019 11:50:46 -0300	[thread overview]
Message-ID: <20190823145046.GG12968@ziepe.ca> (raw)
In-Reply-To: <945643c8-198e-f8bf-1e8f-536f77612db0@golem.network>

On Fri, Aug 23, 2019 at 04:17:50PM +0200, Marcin Mielniczuk wrote:
> While the device is detected by ibv_devices and rping works, I can't get
> ibv_rc_pingpong working
> (and as far as I understand, RC should be supported by the iWARP driver)
> 
> rping works:
> 
>     server$  rping -s -a 10.30.10.211 -v
>     server ping data: rdma-ping-0:
> ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqr
>     server ping data: rdma-ping-1:
> BCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrs
>     server DISCONNECT EVENT...
>     wait for RDMA_READ_ADV state 10
> 
>     client$ rping -c -a 10.30.10.211 -C 2 -v
>     (output omitted)
> 
> 
> But ibv_rc_pingpong doesn't
> 
>     server$ ibv_rc_pingpong -d iwp____
>       local address:  LID 0x0000, QPN 0x000001, PSN 0xb8aafc, GID ::
>     Failed to modify QP to RTS
>     Couldn't connect to remote QP
>     client$ ibv_rc_pingpong  -d iwp____ 10.30.10.211
>       local address:  LID 0x0000, QPN 0x000001, PSN 0x71abc5, GID ::
>     client read/write: Protocol not supported
>     Couldn't read/write remote address

iwarp does not work with the pingpong examples as iwarp requires RDMA
CM and the examples don't use it.

Jason

      reply	other threads:[~2019-08-23 14:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 15:08 Setting up siw devices Marcin Mielniczuk
2019-08-22 15:43 ` Krishnamraju Eraparaju
2019-08-22 15:52   ` Leon Romanovsky
2019-08-22 17:05     ` Marcin Mielniczuk
2019-08-22 17:21       ` Leon Romanovsky
2019-08-22 17:58         ` Marcin Mielniczuk
2019-08-22 18:38           ` Leon Romanovsky
2019-08-22 19:13             ` Jason Gunthorpe
2019-08-22 19:24               ` Leon Romanovsky
2019-08-26 10:02             ` Marcin Mielniczuk
2019-08-26 11:39               ` Leon Romanovsky
2019-08-26 18:21                 ` Marcin Mielniczuk
     [not found]     ` <b4bf4bc2-8dc7-a2c2-6bd2-ab41d9fbadc9@golem.network>
2019-08-23 14:17       ` Marcin Mielniczuk
2019-08-23 14:50         ` Jason Gunthorpe [this message]

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=20190823145046.GG12968@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=krishna2@chelsio.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=marcin@golem.network \
    /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