Skip to contentSkip to conversation

why ibv_wc src_qp is zero

DISCUSSION Liu, Changcheng 2 participants 3 messages Aug 21, 2019 InfiniBand

lore
Share & tools
lore
#0 lore raw

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?

--Thanks
Changcheng

#1 lore raw
Quoted 7 lines · Changcheng

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

#2 lore raw
Quoted 10 lines · Jason Gunthorpe
Quoted 7 lines · Changcheng

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

Thanks a lot for your info. I'll check it the protocol.

--Thanks
Changcheng

Quoted 2 lines

Jason