All of lore.kernel.org
 help / color / mirror / Atom feed
From: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
To: RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Fwd: Re: [rdma-core PATCH] providers/rxe: Replace '%' with '&' in check_qp_queue_full()
Date: Tue, 18 Jan 2022 09:02:59 +0000	[thread overview]
Message-ID: <61E6823E.9090808@fujitsu.com> (raw)

CC: linux-rdma mail list

On 2022/1/14 4:51, Bob Pearson wrote:
> The way these queues work they can only hold 2^n - 1 entries. The reason for this is
> to distinguish empty and full. If you let the last entry be written then producer would advance to equal consumer which is the initial empty condition. So a queue which can hold 1 entry has to have two slots (n=1) but can only hold one entry. It begins with
Hi Bob,

Thanks for your detailed example.
> prod = cons = 0 and is empty and is*not*  full
>
> Adding one entry gives
>
> slot[0] = value, prod = 1, cons = 0 and is full and not empty
>
> After reading this value
>
> slot[0] = old value, prod = cons = 1 and queue is empty again.
>
> Writing a new value
>
> slot[1] = new value, slot[0] = old value, prod = 0 and cons = 1 and queue is full again.
>
> The expression full = (cons == ((qp->cur_index + 1) % q->index_mask)) is correct.
The issue happens here, let's look at the "writing a new value" step.
We think queue is full again when prod = 0 and cons = 1, but this 
expression thinks the queue is not full.
cons == ((qp->cur_index + 1) % q->index_mask))
<1> == <0 + 1>     % <1>

In addition, this expression thinks the queue is full wrongly when we 
create an empty two-slots queue (i.e. prod = 0 and cons = 0).
cons == ((qp->cur_index + 1) % q->index_mask))
<0> == <0 + 1>     % <1>

The following steps can expose the issue:
-------------------------------------------
attr_ex.cap.max_send_wr = attr_ex.cap.max_recv_wr = 1;
...
ret = rdma_create_qp_ex(id, &attr_ex);
...
ibv_wr_start(qpx);
ibv_wr_rdma_atomic_write(qpx,...);  --> check_qp_queue_full() returns 
ENOSPC wrongly.
ibv_wr_complete(qpx);
-------------------------------------------
Please see my example[1] for details.

[1] 
https://github.com/yangx-jy/rdma-core/commit/257c6672dc147e0881525e469a49d933f1bc9183

I think the commit message misled you.

Best Regards,
Xiao Yang
> Please do not make this change.
>
> Bob

             reply	other threads:[~2022-01-18  9:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18  9:02 yangx.jy [this message]
2022-01-20  5:08 ` Fwd: Re: [rdma-core PATCH] providers/rxe: Replace '%' with '&' in check_qp_queue_full() Bob Pearson
2022-01-21  6:20   ` 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=61E6823E.9090808@fujitsu.com \
    --to=yangx.jy@fujitsu.com \
    --cc=linux-rdma@vger.kernel.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 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.