All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Srouji <edwards@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>, <linux-rdma@vger.kernel.org>
Subject: Re: pyverbs regression
Date: Mon, 21 Sep 2020 12:44:34 +0300	[thread overview]
Message-ID: <1fb57743-20fd-1316-8071-cc3ab056e582@nvidia.com> (raw)
In-Reply-To: <5c484f6d-364f-834d-0b16-144be92fc234@gmail.com>

Did you make sure that Pyverbs was recompiled as part of rdma-core 
rebuild? It looks like you've newer rdma-core with older Pyverbs structs.

Also, if you have multiple python versions make sure that Pyverbs was 
installed under the version you're using.

I don't see these inconsistencies, can you please provide which heads 
you're looking at in case you still seeing this?

On 9/18/2020 8:23 PM, Bob Pearson wrote:
> I pulled head of tree for rdma-core and the kernel and rebuilt them and I am now seeing the following warnings from pyverbs which I had not seen before. The tests I expected to run are still running but there seems to be an inconsistency somewhere.
>
> <frozen importlib._bootstrap>:219: RuntimeWarning: pyverbs.srq.SRQ size changed, may indicate binary incompatibility. Expected 56 from C header, got 64 from PyObject
> <frozen importlib._bootstrap>:219: RuntimeWarning: pyverbs.qp.QP size changed, may indicate binary incompatibility. Expected 104 from C header, got 112 from PyObject
> <frozen importlib._bootstrap>:219: RuntimeWarning: pyverbs.qp.QPEx size changed, may indicate binary incompatibility. Expected 112 from C header, got 120 from PyObject
>
> Bob Pearson

  reply	other threads:[~2020-09-21  9:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 17:23 pyverbs regression Bob Pearson
2020-09-21  9:44 ` Edward Srouji [this message]
2020-09-21 16:34   ` Pearson, Robert B
2020-09-25 14:07     ` 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=1fb57743-20fd-1316-8071-cc3ab056e582@nvidia.com \
    --to=edwards@nvidia.com \
    --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 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.