From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Liu, Changcheng" <changcheng.liu@intel.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: why ibv_wc src_qp is zero
Date: Wed, 21 Aug 2019 09:25:54 -0300 [thread overview]
Message-ID: <20190821122554.GA8653@ziepe.ca> (raw)
In-Reply-To: <20190821121436.GA1834@jerryopenix>
On Wed, Aug 21, 2019 at 08:14:36PM +0800, Liu, Changcheng wrote:
> Hi all,
> Does anyone know the usage of the src_qp field in struct ibv_wc?
>
> I’m using RC transport type with only Send Operation on Send Queue.
> On the requester side, when SQ WR is finished, there’s one WCE is on CQ. ibv_wc::src_qp is checked with zero value.
> On the responder side, when RQ WR is finished, there’s one WCE is on CQ. ibv_wc::src_qp is checked with zero value too.
> Why the ibv_wc::src_qp field is zero instead of recording the peer's qp number?
It is only supported for UD QPs
Jason
next prev parent reply other threads:[~2019-08-21 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 12:14 why ibv_wc src_qp is zero Liu, Changcheng
2019-08-21 12:25 ` Jason Gunthorpe [this message]
2019-08-21 12:30 ` Liu, Changcheng
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=20190821122554.GA8653@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=changcheng.liu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox