From: Zhu Yanjun <zyjzyj2000@gmail.com>
To: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
Cc: Olga Kornievskaia <aglo@umich.edu>,
Leon Romanovsky <leon@kernel.org>,
Bob Pearson <rpearsonhpe@gmail.com>,
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 11:31:53 +0800 [thread overview]
Message-ID: <CAD=hENeYiTrfxDTAS9UkF8tn7=wa49H0DQuCBKeHpd+L6qM4SQ@mail.gmail.com> (raw)
In-Reply-To: <611D1A3E.20701@fujitsu.com>
On Wed, Aug 18, 2021 at 10:33 PM yangx.jy@fujitsu.com
<yangx.jy@fujitsu.com> wrote:
>
> On 2021/8/18 16:28, Zhu Yanjun wrote:
> > On Wed, Aug 18, 2021 at 3:44 PM yangx.jy@fujitsu.com
> > <yangx.jy@fujitsu.com> wrote:
> >> On 2021/8/18 15:20, Zhu Yanjun wrote:
> >>> Can you let me know how to reproduce the panic?
> >>>
> >>> 1. linux upstream< ----rping----> linux upstream?
> >> rdma_client on v5.13< ---> rdma_server on upstream kernel.
> >>
> >>> 2. just run rping?
> >> Running rdma_client on v5.13 and rdma_server on upstream can reproduce
> >> the issue.
> >>
> >> Note: running rping can reproduce the issue as well.
> > rping and rdma_server/rdma_client are from the latest rdma-core?
> Yes, use the latest rdma-core from
> https://github.com/linux-rdma/rdma-core (master branch).
Latest kernel + latest rdma-core < ------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.
Zhu Yanjun
> > Thanks
> > Zhu Yanjun
> >
> >>> 3. how do you create rxe? with rdma link or rxe_cfg?
> >> rdma link add
> >>> 4. do you make other operations?
> >> No
> >>> 5. other operations?
> >> No
> >>> Thanks.
> >>> Zhu Yanjun
> >>>
next prev parent reply other threads:[~2021-08-20 3:32 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 [this message]
2021-08-20 7:42 ` yangx.jy
2021-08-20 21:40 ` Bob Pearson
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='CAD=hENeYiTrfxDTAS9UkF8tn7=wa49H0DQuCBKeHpd+L6qM4SQ@mail.gmail.com' \
--to=zyjzyj2000@gmail.com \
--cc=aglo@umich.edu \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
--cc=yangx.jy@fujitsu.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.