From: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
To: Leon Romanovsky <leon@kernel.org>,
"rpearsonhpe@gmail.com" <rpearsonhpe@gmail.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH rdma-core RESEND] providers/rxe: Replace '%' with '&' in check_qp_queue_full()
Date: Tue, 11 Jan 2022 09:19:46 +0000 [thread overview]
Message-ID: <61DD4BB0.7070306@fujitsu.com> (raw)
In-Reply-To: <Yd0fpzSbzWPv1TS0@unreal>
On 2022/1/11 14:11, Leon Romanovsky wrote:
> On Tue, Jan 11, 2022 at 10:24:04AM +0800, Xiao Yang wrote:
>> The expression "cons == ((qp->cur_index + 1) % q->index_mask)" mistakenly
>> assumes the queue is full when the number of entires is equal to "maximum - 1"
>> (maximum is correct).
>>
>> For example:
>> If cons and qp->cur_index are 0 and q->index_mask is 1, check_qp_queue_full()
>> reports ENOSPC.
>>
>> Fixes: 1a894ca10105 ("Providers/rxe: Implement ibv_create_qp_ex verb")
>> Signed-off-by: Xiao Yang<yangx.jy@fujitsu.com>
>> ---
>> providers/rxe/rxe_queue.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/providers/rxe/rxe_queue.h b/providers/rxe/rxe_queue.h
>> index 6de8140c..708e76ac 100644
>> --- a/providers/rxe/rxe_queue.h
>> +++ b/providers/rxe/rxe_queue.h
>> @@ -205,7 +205,7 @@ static inline int check_qp_queue_full(struct rxe_qp *qp)
>> if (qp->err)
>> goto err;
>>
>> - if (cons == ((qp->cur_index + 1) % q->index_mask))
>> + if (cons == ((qp->cur_index + 1)& q->index_mask))
> Please reuse queue_full().
Hi Leon,
qp->cur_index and qp->err are introduced for new ibv_wr_* APIs and I am
not sure if check_qp_queue_full() can be replaced with queue_full().
Bob, do you have any suggestion?
Best Regards,
Xiao Yang
> Thanks
>
>> qp->err = ENOSPC;
>> err:
>> return qp->err;
>> --
>> 2.25.1
>>
>>
>>
next prev parent reply other threads:[~2022-01-11 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 2:24 [PATCH rdma-core RESEND] providers/rxe: Replace '%' with '&' in check_qp_queue_full() Xiao Yang
2022-01-11 4:12 ` Devesh Sharma
2022-01-11 9:10 ` yangx.jy
2022-01-11 10:21 ` Devesh Sharma
2022-01-11 6:11 ` Leon Romanovsky
2022-01-11 9:19 ` yangx.jy [this message]
2022-01-11 10:47 ` Leon Romanovsky
2022-01-12 3:39 ` yangx.jy
2022-01-18 8:37 ` yangx.jy
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=61DD4BB0.7070306@fujitsu.com \
--to=yangx.jy@fujitsu.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@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).