From: Bob Pearson <rpearsonhpe@gmail.com>
To: Edward Srouji <edwards@nvidia.com>,
jgg@nvidia.com, linux-rdma@vger.kernel.org
Subject: Re: modify srq pyverbs test (new?) failing for the rxe driver
Date: Wed, 25 Oct 2023 10:49:14 -0500 [thread overview]
Message-ID: <ec603876-6872-4e8e-9490-e28f7cca8c6d@gmail.com> (raw)
In-Reply-To: <b4ee7c64-720e-5580-ce25-5d7c7991fca4@nvidia.com>
On 10/25/23 06:29, Edward Srouji wrote:
> You're right.
> I've patched the test and pushed it Upstream (see PR link below [1]).
> Please notify me if you're still having an issue after applying the patch.
Will do. Thanks!
Bob
>
> On 10/24/2023 8:47 PM, Bob Pearson wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> On 10/23/23 17:47, Bob Pearson wrote:
>>> Edward,
>>>
>>> There is a test which may be new since this failure didn't happen
>>> before. Modify srq tries to set max_wr to 4094 but the rxe driver
>>> rounds this up to 2^n-1 or 4095. My understanding of the IBA
>>> spec is that queue sizes can be set larger than requested.
>>> Also this same test tries to change max_sge using the same
>>> MAX_WR mask bit. There is no mention (as far as I can recall)
>>> in the IBA spec of being able to change the max_sge setting.
>>>
>>> Is this really the correct behavior?
>>>
>>> Bob Pearson
next prev parent reply other threads:[~2023-10-25 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <401221fd-b41d-4db9-be22-b1af17b0d456@gmail.com>
2023-10-24 17:47 ` modify srq pyverbs test (new?) failing for the rxe driver Bob Pearson
2023-10-25 11:29 ` Edward Srouji
2023-10-25 15:49 ` Bob Pearson [this message]
2023-10-26 2:12 ` 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=ec603876-6872-4e8e-9490-e28f7cca8c6d@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=edwards@nvidia.com \
--cc=jgg@nvidia.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.