All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Pearson <rpearsonhpe@gmail.com>
To: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>,
	Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: Olga Kornievskaia <aglo@umich.edu>,
	Leon Romanovsky <leon@kernel.org>,
	Jason Gunthorpe <jgg@nvidia.com>,
	linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: RXE status in the upstream rping using rxe
Date: Fri, 20 Aug 2021 16:40:47 -0500	[thread overview]
Message-ID: <3ef95380-ea42-562a-975d-d767d76ee2ca@gmail.com> (raw)
In-Reply-To: <611F5CD8.2020504@fujitsu.com>

On 8/20/21 2:42 AM, yangx.jy@fujitsu.com wrote:
> On 2021/8/20 11:31, Zhu Yanjun wrote:
>> Latest kernel + latest rdma-coOnre<  ------rping---->  5.10.y stable +
>> latest rdma-core
>> Latest kernel + latest rdma-core<  ------rping---->  5.11.y stable +
>> latest rdma-core
>> Latest kernel + latest rdma-core<  ------rping---->  5.12.y stable +
>> latest rdma-core
>> Latest kernel + latest rdma-core<  ------rping---->  5.13.y stable +
>> latest rdma-core
>>
>> The above works well.
> Hi Yanjun,
> 
> Sorry, I don't know why you cannot reproduce the bug.
> 
> Did you see the similar bug reported by Olga Kornievskaia?
> https://www.spinics.net/lists/linux-rdma/msg104358.html
> https://www.spinics.net/lists/linux-rdma/msg104359.html
> https://www.spinics.net/lists/linux-rdma/msg104360.html
> 
> Best Regards,
> Xiao Yang
>> Zhu Yanjun
>>

There is some interest in the current status of rping on rxe.
I have looked at several configurations and tested the following test cases:

	1. The python test suite in rdma-core
	2. ib_xxx_bw and ib_xxx_bw -R for RC
	3. rping

Between the following node configurations.

	A. 5.11.0 (ubuntu 21.04 OOB) + rdma-core 33.1 (ubuntu 21.04 OOB)
	B. 5.11.0 + current rdma-core
		+ "Provider/rxe:Set the correct value of resid for inline data" (a.k.a rdma-core+)
	C. 5.14.0-rc1+ (for-next current)
		+ 5 recent bug fixes (a.k.a. for-next+)
			RDMA/rxe:Fix bug in get srq wqe in rxe_resp.c.patch

			RDMA/rxe:Fix bug in rxe_net.c.patch

			RDMA/rxe:Add memory barriers to kernel queues.patch

			RDMA/rxe:Fix memory allocation while locked.patch

			RDMA/rxe:Zero out index member of struct rxe_queue.patch
		+ rdma-core+
	D. for-next+ + rdma-core (33.1)

Results:
	1.  A N/A
	1.  B no errors, some skips
	1.  C no errors, some skips
	1.  D N/A
	(n.b. requires adding IPV6 address == gid[0] by hand)

	2. [A-D] -> [A-D] all pass

	3.  A -> A, C -> C, D -> D all pass, all other combinations fail

	(RDMA_resolve_route: No such device. Not yet sure cause of failures but looking into it.)
	In theory these should all work but rdmacm is more sensitive to configuration than verbs. 

Bob


  reply	other threads:[~2021-08-20 21:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 18:07 RXE status in the upstream rping using rxe Leon Romanovsky
2021-08-04  1:01 ` Zhu Yanjun
2021-08-04  1:09   ` Zhu Yanjun
2021-08-04  5:41     ` Leon Romanovsky
2021-08-04  9:05       ` Zhu Yanjun
2021-08-06  2:37         ` Olga Kornievskaia
2021-08-17  2:28           ` Zhu Yanjun
2021-08-18  6:43             ` yangx.jy
2021-08-18  7:20               ` Zhu Yanjun
2021-08-18  7:44                 ` yangx.jy
2021-08-18  8:28                   ` Zhu Yanjun
2021-08-18 14:33                     ` yangx.jy
2021-08-20  3:31                       ` Zhu Yanjun
2021-08-20  7:42                         ` yangx.jy
2021-08-20 21:40                           ` Bob Pearson [this message]
2021-08-20 22:09                             ` Bob Pearson
2021-08-13 21:53         ` Bob Pearson
2021-08-14  5:32           ` Leon Romanovsky
2021-08-23  7:53 ` Zhu Yanjun

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=3ef95380-ea42-562a-975d-d767d76ee2ca@gmail.com \
    --to=rpearsonhpe@gmail.com \
    --cc=aglo@umich.edu \
    --cc=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=yangx.jy@fujitsu.com \
    --cc=zyjzyj2000@gmail.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.