From: "Pearson, Robert B" <robert.pearson2@hpe.com>
To: Shoaib Rao <rao.shoaib@oracle.com>, Jason Gunthorpe <jgg@ziepe.ca>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: RE: [PATCH v3 0/1] RDMA/rxe: Bump up default maximum values used via uverbs
Date: Mon, 13 Sep 2021 03:34:36 +0000 [thread overview]
Message-ID: <CS1PR8401MB1077464FBC2736A93E1D9414BCD99@CS1PR8401MB1077.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <f3849d06-f25b-5119-f2be-4974a72f9bad@oracle.com>
Sorry. I totally missed this. I will look at it in the morning.
Bob
-----Original Message-----
From: Shoaib Rao <rao.shoaib@oracle.com>
Sent: Sunday, September 12, 2021 7:50 PM
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Pearson, Robert B <robert.pearson2@hpe.com>; Zhu Yanjun <zyjzyj2000@gmail.com>; RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH v3 0/1] RDMA/rxe: Bump up default maximum values used via uverbs
On 8/6/21 6:49 AM, Jason Gunthorpe wrote:
> On Wed, Aug 04, 2021 at 11:11:15PM -0700, Shoaib Rao wrote:
>> Bob,
>>
>> Your third patch has an issue.
>>
>> In rxe_cq_post()
>>
>>
>> addr = producer_addr(cq->queue, QUEUE_TYPE_TO_CLIENT);
>>
>> It should be
>>
>> addr = producer_addr(cq->queue, QUEUE_TYPE_FROM_CLIENT);
>>
>> After making this change, I have tested my patch and rping works.
>>
>> Bob can you please point me to the discussion which lead to the
>> current changes, particularly the need for user barrier.
>>
>> Zhu can you apply Bob's 3 patches + the change above + my patch and
>> report back. In my testing it works.
> I'll expect Bob to resend
>
> [for-next,v2,3/3] RDMA/rxe: Add memory barriers to kernel queues
>
> Jason
I have not seen a reply to this email thread. Has the issue been resolved and I missed it?
Shoaib
next prev parent reply other threads:[~2021-09-13 3:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 22:59 [PATCH v3 0/1] RDMA/rxe: Bump up default maximum values used via uverbs Rao Shoaib
2021-07-18 22:59 ` [PATCH v3 1/1] " Rao Shoaib
2021-07-27 16:15 ` [PATCH v3 0/1] " Shoaib Rao
2021-07-27 17:41 ` Jason Gunthorpe
2021-07-29 6:42 ` Zhu Yanjun
2021-07-29 6:52 ` Shoaib Rao
2021-07-29 7:57 ` Zhu Yanjun
2021-07-29 19:33 ` Shoaib Rao
2021-07-29 19:50 ` Jason Gunthorpe
2021-07-29 20:33 ` Shoaib Rao
2021-07-29 23:08 ` Pearson, Robert B
2021-07-30 0:34 ` Shoaib Rao
2021-08-03 23:53 ` Shoaib Rao
2021-08-04 0:51 ` Zhu Yanjun
2021-08-04 1:51 ` Shoaib Rao
2021-08-04 2:21 ` Zhu Yanjun
2021-08-05 4:10 ` Shoaib Rao
2021-08-05 6:56 ` Leon Romanovsky
2021-08-05 6:11 ` Shoaib Rao
2021-08-06 13:49 ` Jason Gunthorpe
2021-09-13 0:50 ` Shoaib Rao
2021-09-13 3:34 ` Pearson, Robert B [this message]
2021-09-14 16:14 ` 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=CS1PR8401MB1077464FBC2736A93E1D9414BCD99@CS1PR8401MB1077.NAMPRD84.PROD.OUTLOOK.COM \
--to=robert.pearson2@hpe.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=rao.shoaib@oracle.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 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).