From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Yonatan Cohen <yonatanc-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: GAFBlizzard <gtschemer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Youngjae Lee <dhrkaeh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Josh Beavers
<josh.beavers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: ibv_rc_pingpong, rping, and other tools hang with Linux 4.10.0 and rdma-core 13
Date: Mon, 27 Feb 2017 09:29:16 -0700 [thread overview]
Message-ID: <20170227162916.GC5891@obsidianresearch.com> (raw)
In-Reply-To: <4e077022-5e5f-6ba8-530c-b86d2f09313e-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On Sun, Feb 26, 2017 at 06:09:34PM +0200, Yonatan Cohen wrote:
> I bisected the rdma-core library and figured out that the following commit
> introduced this regression:
> 6b26a9e24739 Use C11 atomics instead of wmb/rmb macros for CPU-only atomics
>
> I haven't debugged this yet and would appreciate Jason's input.
Oops, I think I typo'd it here:
--- a/providers/rxe/rxe_queue.h
+++ b/providers/rxe/rxe_queue.h
@@ -37,15 +37,16 @@
#ifndef H_RXE_PCQ
#define H_RXE_PCQ
+#include <stdatomic.h>
+
/* MUST MATCH kernel struct rxe_pqc in rxe_queue.h */
struct rxe_queue {
uint32_t log2_elem_size;
uint32_t index_mask;
uint32_t pad_1[30];
- volatile uint32_t producer_index;
+ _Atomic(uint32_t) producer_index;
uint32_t pad_2[31];
- volatile uint32_t consumer_index;
- uint32_t pad_3[31];
+ _Atomic(uint32_t) consumer_index;
Ie deleted pad_3[31] by mistake!
My bad
Jason
--
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
next prev parent reply other threads:[~2017-02-27 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 3:27 ibv_rc_pingpong, rping, and other tools hang with Linux 4.10.0 and rdma-core 13 GAFBlizzard
[not found] ` <CABQspYbv7j58pdLLbPegE8Bc3qhwb-3+4E8SQ2U9jObkeTbrzw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-26 16:09 ` Yonatan Cohen
[not found] ` <4e077022-5e5f-6ba8-530c-b86d2f09313e-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-02-27 16:29 ` Jason Gunthorpe [this message]
[not found] ` <20170227162916.GC5891-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-02-27 20:38 ` Majd Dibbiny
-- strict thread matches above, loose matches on Subject: below --
2017-02-27 17:02 Josh Beavers
[not found] ` <CAE=AiOMqGzMC6sD-cXB_sGRH_L15annm_4WottmY17oCSNZveA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-27 17:15 ` Jason Gunthorpe
[not found] ` <20170227171549.GG5891-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-02-27 18:59 ` Jason Gunthorpe
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=20170227162916.GC5891@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=dhrkaeh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=gtschemer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=josh.beavers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yonatanc-VPRAkNaXOzVWk0Htik3J/w@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