linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Pearson <rpearsonhpe@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>,
	"Pearson, Robert B" <robert.pearson2@hpe.com>,
	"jgg@nvidia.com" <jgg@nvidia.com>,
	"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"mie@igel.co.jp" <mie@igel.co.jp>
Subject: Re: [PATCH for-rc v3 0/6] RDMA/rxe: Various bug fixes.
Date: Fri, 10 Sep 2021 16:50:16 -0500	[thread overview]
Message-ID: <598ffc9f-1971-0b46-f2fc-68ed21fb2f1c@gmail.com> (raw)
In-Reply-To: <cf358367-5cb8-0482-28e6-993a4f6bb047@gmail.com>

On 9/10/21 4:47 PM, Bob Pearson wrote:
> On 9/10/21 3:23 PM, Bart Van Assche wrote:
>> On 9/10/21 12:38 PM, Pearson, Robert B wrote:
>>> 1. Which rdma-core are you running? Out of box or the github tree?
>>
>> I'm using the rdma-core package included in openSUSE Tumbleweed. blktests
>> pass with that rdma-core package against older kernel versions so I think
>> the rdma-core package is fine. The version number of the rdma-core package
>> I'm using is as follows:
>> $ rpm -q rdma-core
>> rdma-core-36.0-1.1.x86_64
>>
>> The rdma tool comes from the iproute2 package:
>> $ rpm -qf /sbin/rdma
>> iproute2-5.13-1.1.x86_64
>>
>>> 3. Where did you get the kernel bits? Which git tree? Which branch?
>>
>> Hmm ... wasn't that mentioned in my previous email? I mentioned a commit
>> SHA and these SHA numbers are unique and unambiguous. Anyway: commit
>> 2169b908894d comes from the for-rc branch of the following git repository:
>> git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git.
>>
>> Bart.
>>
>>
> 
> OK I checked out the kernel with the SHA number above and applied the patch series
> and rebuilt and reinstalled the kernel. I checked out v36.0 of rdma-core and rebuilt
> that. rdma is version 5.9.0 but I doubt that will have any effect. My startup script
> is
> 
>     export LD_LIBRARY_PATH=/home/bob/src/rdma-core/build/lib/:/usr/local/lib:/usr/lib
> 
> 
> 
>     sudo ip link set dev enp0s3 mtu 8500
> 
>     sudo ip addr add dev enp0s3 fe80::0a00:27ff:fe94:8a69/64
> 
>     sudo rdma link add rxe0 type rxe netdev enp0s3
> 
> 
> I am running on a Virtualbox VM instance of Ubuntu 21.04 with 20 cores and 8GB of RAM.
> 
> The test looks like
> 
>     sudo ./check -q srp/001
> 
>     srp/001 (Create and remove LUNs)                             [passed]
> 
>         runtime  1.174s  ...  1.236s
> 
> There were no issues. 
> 
> Any guesses what else to look at?
> 
> Thanks,
> 
> Bob
> 

The 8500 is not required. It runs fine with 4K MTU just as well.

  reply	other threads:[~2021-09-10 21:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 20:44 Bob Pearson
2021-09-09 20:44 ` [PATCH for-rc v3 1/6] RDMA/rxe: Add memory barriers to kernel queues Bob Pearson
2021-09-10  1:19   ` Zhu Yanjun
2021-09-10  4:01     ` Bob Pearson
2021-09-14  6:04   ` 回复: " yangx.jy
2021-09-14 15:47     ` Bob Pearson
2021-09-09 20:44 ` [PATCH for-rc v3 2/6] RDMA/rxe: Fix memory allocation while locked Bob Pearson
2021-09-09 20:44 ` [PATCH for-rc v3 3/6] RDMA/rxe: Cleanup MR status and type enums Bob Pearson
2021-09-09 20:44 ` [PATCH for-rc v3 4/6] RDMA/rxe: Separate HW and SW l/rkeys Bob Pearson
2021-09-09 20:44 ` [PATCH for-rc v3 5/6] RDMA/rxe: Create duplicate mapping tables for FMRs Bob Pearson
2021-09-09 20:44 ` [PATCH for-rc v3 6/6] RDMA/rxe: Only allow invalidate for appropriate MRs Bob Pearson
2021-09-09 21:52 ` [PATCH for-rc v3 0/6] RDMA/rxe: Various bug fixes Bart Van Assche
2021-09-10 19:38   ` Pearson, Robert B
2021-09-10 20:23     ` Bart Van Assche
2021-09-10 21:16       ` Bob Pearson
2021-09-10 21:47       ` Bob Pearson
2021-09-10 21:50         ` Bob Pearson [this message]
2021-09-10 22:07         ` Bart Van Assche
2021-09-12 14:41           ` Bob Pearson
2021-09-14  3:26             ` Bart Van Assche
2021-09-14  4:18               ` Bob Pearson
2021-09-12 14:42           ` Bob Pearson

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=598ffc9f-1971-0b46-f2fc-68ed21fb2f1c@gmail.com \
    --to=rpearsonhpe@gmail.com \
    --cc=bvanassche@acm.org \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mie@igel.co.jp \
    --cc=robert.pearson2@hpe.com \
    --cc=zyjzyj2000@gmail.com \
    --subject='Re: [PATCH for-rc v3 0/6] RDMA/rxe: Various bug fixes.' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).