From: Leon Romanovsky <leon@kernel.org>
To: Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: Olga Kornievskaia <aglo@umich.edu>,
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: Wed, 4 Aug 2021 08:41:20 +0300 [thread overview]
Message-ID: <YQoogK7uWCLHUzcs@unreal> (raw)
In-Reply-To: <CAD=hENfua2UXH6rVuhMPXYsNSavqG==T3h=z4f=huf+Fj+xiHA@mail.gmail.com>
On Wed, Aug 04, 2021 at 09:09:41AM +0800, Zhu Yanjun wrote:
> On Wed, Aug 4, 2021 at 9:01 AM Zhu Yanjun <zyjzyj2000@gmail.com> wrote:
> >
> > On Wed, Aug 4, 2021 at 2:07 AM Leon Romanovsky <leon@kernel.org> wrote:
> > >
> > > Hi,
> > >
> > > Can you please help me to understand the RXE status in the upstream?
> > >
> > > Does we still have crashes/interop issues/e.t.c?
> >
> > I made some developments with the RXE in the upstream, from my usage
> > with latest RXE,
> > I found the following:
> >
> > 1. rdma-core can not work well with latest RDMA git;
>
> The latest RDMA git is
> https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git
"Latest" is a relative term, what SHA did you test?
Let's focus on fixing RXE before we will continue with new features.
Thanks
next prev parent reply other threads:[~2021-08-04 5:41 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 [this message]
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
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=YQoogK7uWCLHUzcs@unreal \
--to=leon@kernel.org \
--cc=aglo@umich.edu \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.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.