From: Bob Pearson <rpearsonhpe@gmail.com>
To: Zhu Yanjun <zyjzyj2000@gmail.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-rdma@vger.kernel.org, Bob Pearson <rpearson@hpe.com>
Subject: Re: [PATCH for-next v5 00/12] rdma_rxe: API extensions
Date: Sun, 20 Sep 2020 16:13:29 -0500 [thread overview]
Message-ID: <f6803def-13b8-04f0-5fd0-cbad702f1837@gmail.com> (raw)
In-Reply-To: <088207e0-bdaf-0d0c-62b9-612941825ca8@gmail.com>
On 9/19/20 3:46 AM, Zhu Yanjun wrote:
> On 9/19/2020 4:44 PM, Zhu Yanjun wrote:
>>
>> On 9/19/2020 7:51 AM, Jason Gunthorpe wrote:
>>> On Fri, Sep 18, 2020 at 04:15:05PM -0500, Bob Pearson wrote:
>>>> This patch series is a collection of API extensions for the rdma_rxe driver.
>>>> With this patch set installed there are no errors in pyverbs run-tests and
>>>> 31 tests are skipped down from 56. The remaining skipped test cases include
>>>> - XRC tests
>>>> - ODP tests
>>>> - Parent device tests
>>>> - Import tests
>>>> - Device memory
>>>> - MLX5 specific tests
>>>> - EFA tests
>>> It seems like a big improvement! Thanks!
>>>
>>> Zhu, can you look through this too?
>>
>> OK. It seems that a problem occurred in this patch set.
>>
>> Hi, Bob
>>
>> Please fix this problem. Thanks a lot.
>
> The problem mail is in the attachment. Please check and fix it.
>
> Zhu Yanjun
>
>>
>> Zhu Yanjun
>>
>>>
>>> Jason
>>>
>>>> It continues from the previous (v4) set which implemented memory windows and
>>>> has had a number of individual patches picked up in for-next.
>>>>
>>>> This set (v5) includes:
>>>> Ported to current head of tree
>>>> Memory windows patches not yet picked up
>>>> kernel support for the extended user space APIs:
>>>> - ibv_query_device_ex
>>>> - ibv_create_cq_ex
>>>> - ibv_create_qp_ex
>>>> Fixes for multicast which is not currently working
>>> I would like to progress the simple independent obviously OK bits,
>>> could you split them out?
>>>
>>> Jason
>
>
Zhu,
The missing prototype was a good catch. (That is resolved now.) But I can't figure out the null pointer arithmetic warnings. They are all in obscure distant header files. Do you have any insight about those?
Bob
next prev parent reply other threads:[~2020-09-20 21:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 21:15 [PATCH for-next v5 00/12] rdma_rxe: API extensions Bob Pearson
2020-09-18 21:15 ` [PATCH for-next v5 01/12] rdma_rxe: Separat MEM into MR and MW objects Bob Pearson
2020-09-18 21:15 ` [PATCH for-next v5 02/12] rdma_rxe: Enable " Bob Pearson
2020-09-18 21:15 ` [PATCH for-next v5 03/12] rdma_rxe: Let pools support both keys and indices Bob Pearson
2020-09-18 21:15 ` [PATCH for-next v5 04/12] rdma_rxe: Add alloc_mw and dealloc_mw verbs Bob Pearson
2020-09-18 21:15 ` [PATCH for-next v5 05/12] rdma_rxe: Add bind_mw and invalidate_mw verbs Bob Pearson
2020-09-18 21:15 ` [PATCH for-next v5 06/12] rdma_rxe: Add memory access through MWs Bob Pearson
2020-09-19 3:52 ` kernel test robot
2020-09-18 21:15 ` [PATCH for-next v5 07/12] rdma_rxe: Add support for ibv_query_device_ex Bob Pearson
2020-09-18 23:40 ` Jason Gunthorpe
2020-09-18 21:15 ` [PATCH for-next v5 08/12] rdma_rxe: Add support for extended CQ operations Bob Pearson
2020-09-18 21:15 ` [PATCH for-next v5 09/12] rdma_rxe: Add support for extended QP operations Bob Pearson
2020-09-18 23:40 ` Jason Gunthorpe
2020-09-18 21:15 ` [PATCH for-next v5 10/12] rdma_rxe: Fix pool related bugs Bob Pearson
2020-09-18 23:49 ` Jason Gunthorpe
2020-09-18 21:15 ` [PATCH for-next v5 11/12] rdma_rxe: Fix mcast group allocation bug Bob Pearson
2020-09-18 21:15 ` [PATCH for-next v5 12/12] rdma_rxe: Fix bugs in the multicast receive path Bob Pearson
2020-09-18 23:51 ` [PATCH for-next v5 00/12] rdma_rxe: API extensions Jason Gunthorpe
2020-09-19 8:44 ` Zhu Yanjun
2020-09-19 8:46 ` Zhu Yanjun
2020-09-20 21:13 ` Bob Pearson [this message]
2020-09-21 14:10 ` 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=f6803def-13b8-04f0-5fd0-cbad702f1837@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearson@hpe.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).