All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pearson, Robert B" <rpearsonhpe@gmail.com>
To: Zhu Yanjun <zyjzyj2000@gmail.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: zyj2000@gmail.com, RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH for-next v8 00/10] RDMA/rxe: Implement memory windows
Date: Fri, 4 Jun 2021 12:53:51 -0500	[thread overview]
Message-ID: <8ae22b01-51e0-4115-31a5-ff9c1378efb6@gmail.com> (raw)
In-Reply-To: <0c9c8709-8816-6083-59ef-c8d664ba382c@gmail.com>


On 6/4/2021 11:22 AM, Pearson, Robert B wrote:
>
> On 6/4/2021 12:37 AM, Zhu Yanjun wrote:
>>
>> After I added a rxe device on the netdev, then run rdma-core test tools.
>> Then I remove rxe device, in the end, I unloaded rdma_rxe kernel 
>> modules.
>> I found the above logs.
>> "
>> [ 1249.651921] rdma_rxe: rxe-pd pool destroyed with unfree'd elem
>> [ 1249.651927] rdma_rxe: rxe-qp pool destroyed with unfree'd elem
>> [ 1249.651929] rdma_rxe: rxe-cq pool destroyed with unfree'd elem
>> "
>>
>> It seems that  some resources leak.
>>
>> I will make further investigations.
>>
>> Zhu Yanjun
>
> Zhu,
>
> I suspect this is an older error. I traced all the add and drop ref 
> calls for PDs, then ran the full suite of Python tests and also 
> test_mr which includes the memory window tests by itself and then 
> counted the adds and drops. For test_mr alone I get 85 adds and 85 
> drops but when I run the whole suite I get 384 adds and 380 drops. 
> Since the memory window code is only exercised in test_mr I think it 
> is OK. Somewhere else there are missing drops. I will try to isolate 
> them.
>
> Bob
>
Zhu,

In rdma_core/tests/test_qpex.py test_qp_ex_rc_atomic_cmp_swp and 
test_qp_ex_rc_atomic_fetch_add each have two missing drops of PDs. This 
is either a test bug or a bug in the rxe driver but it has nothing to do 
with the MW code. We should treat it as a separate error. For some 
reason these test cases are not cleaning up all resources.

The cleanup code in all these Python tests is very implicit. It just 
happens by magic so it is hard to figure out where an ibv_destroy_qp or 
ibv_destroy_cq went missing. It would help if someone who is familiar 
with these tests could look at it.

Bob


  reply	other threads:[~2021-06-04 17:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 21:37 [PATCH for-next v8 00/10] RDMA/rxe: Implement memory windows Bob Pearson
2021-05-25 21:37 ` [PATCH for-next v8 1/9] RDMA/rxe: Add bind MW fields to rxe_send_wr Bob Pearson
2021-05-25 21:37 ` [PATCH for-next v8 02/10] RDMA/rxe: Return errors for add index and key Bob Pearson
2021-05-25 21:37 ` [PATCH for-next v8 03/10] RDMA/rxe: Enable MW object pool Bob Pearson
2021-05-25 21:37 ` [PATCH for-next v8 04/10] RDMA/rxe: Add ib_alloc_mw and ib_dealloc_mw verbs Bob Pearson
2021-05-25 21:37 ` [PATCH for-next v8 05/10] RDMA/rxe: Replace WR_REG_MASK by WR_LOCAL_OP_MASK Bob Pearson
2021-05-25 21:37 ` [PATCH for-next v8 06/10] RDMA/rxe: Move local ops to subroutine Bob Pearson
2021-05-25 21:37 ` [PATCH for-next v8 07/10] RDMA/rxe: Add support for bind MW work requests Bob Pearson
2021-05-25 21:37 ` [PATCH for-next v8 08/10] RDMA/rxe: Implement invalidate MW operations Bob Pearson
2021-05-25 21:37 ` [PATCH for-next v8 09/10] RDMA/rxe: Implement memory access through MWs Bob Pearson
2021-05-25 21:37 ` [PATCH for-next v8 10/10] RDMA/rxe: Disallow MR dereg and invalidate when bound Bob Pearson
2021-06-03 18:58 ` [PATCH for-next v8 00/10] RDMA/rxe: Implement memory windows Jason Gunthorpe
2021-06-04  3:22   ` Pearson, Robert B
2021-06-04  5:37   ` Zhu Yanjun
2021-06-04 15:25     ` Pearson, Robert B
2021-06-04 16:22     ` Pearson, Robert B
2021-06-04 17:53       ` Pearson, Robert B [this message]
2021-06-04 17:55         ` Jason Gunthorpe
2021-06-04 19:26           ` Pearson, Robert B

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=8ae22b01-51e0-4115-31a5-ff9c1378efb6@gmail.com \
    --to=rpearsonhpe@gmail.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=zyj2000@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.