public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Matan Barak' <matanb-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: 'linux-rdma' <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: RE: ib_uverbs: list corruption destroying a cq
Date: Wed, 26 Jul 2017 11:34:54 -0500	[thread overview]
Message-ID: <00e301d3062d$1c7a2be0$556e83a0$@opengridcomputing.com> (raw)
In-Reply-To: <CAAKD3BCkZVcMbvyMPVF75Kg0wU4Ld7cByMTWRrydgsyqjCuS9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

> 
> Hi Steve,
> 
> AFAIK, we haven't seen anything like this. A few questions:
> 1. Does your test use multiple threads from which it executes uverbs commands?

Yes.  This particular test runs 6 processes, each setting up hundreds of connections and divvying up the workload among many threads.  Over 100 threads (the poor host probably has 8 cpus :)).

> 2. Does your test use completion channel?

Not in this instance; polling only.  Each connection gets its own cq for both the RQ and SQ of its QP.

> 3. Which rdma device are you using?

iw_cxgb4

> 4. Do you know approximately in which kernel version this warning started?

I believe 4.13-rc.  But I'm not certain. 

> 5. Is it reproducible?

They hit it once after ~4 hours so far, and the tests keep running subsequent instances.

> 6. Are you willing to send the actual test?
>

I don't think that's possible.  


I'll keep debugging, but was wondering if anyone has seen this already in 4.13-rc.  

Thanks Matan!

Steve.


--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-07-26 16:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26 15:52 ib_uverbs: list corruption destroying a cq Steve Wise
2017-07-26 16:27 ` Matan Barak
     [not found]   ` <CAAKD3BCkZVcMbvyMPVF75Kg0wU4Ld7cByMTWRrydgsyqjCuS9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-26 16:34     ` Steve Wise [this message]
2017-07-26 16:43 ` Jason Gunthorpe
2017-07-26 18:12 ` Robert LeBlanc

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='00e301d3062d$1c7a2be0$556e83a0$@opengridcomputing.com' \
    --to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matanb-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox