From: Leon Romanovsky <leon@kernel.org>
To: Haakon Bugge <haakon.bugge@oracle.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
OFED mailing list <linux-rdma@vger.kernel.org>
Subject: Re: Seeking clarification on the XRC Annex wrt. a TGT QP having a SQ
Date: Mon, 7 Feb 2022 20:59:25 +0200 [thread overview]
Message-ID: <YgFsDXH5XdEBOT/O@unreal> (raw)
In-Reply-To: <6FD25F7D-6F5A-4990-A179-5ED213001BB7@oracle.com>
On Mon, Feb 07, 2022 at 02:55:35PM +0000, Haakon Bugge wrote:
> Hey,
>
>
> I have a question to XRC TGT QPs and whether they do have a set of requestor resources or not.
>
>
> The XRC Annex (March 2, 2009 Revision 1.0) (*1) boldly states:
>
> XRC TGT QPs are similar to RD EECs but do not have a requester side.
>
>
> Nevertheless, in Table 9, page 36, it is stated that "Local ACK Timeout" and "SQ PSN" are required attributes during an RTR -> RTS transition for an XRC Target QP. This seems to be an incorrect requirement, subject to the XRC Target QP not having a send queue?
>
> Further, looking at a vendor's creation of an XRC TGT QP, we see:
>
> MLX5_SET(qpc, qpc, no_sq, 1);
>
> in the function create_xrc_tgt().
>
> If the interpretation that an XRC TGT does _not_ have a send queue is correct, we cannot simply remove "Local ACK Timeout" and "SQ PSN" as mandatory attributes during the state transition, because that will break all current software. Is it an idea to move those to optional attributes in the qp_state_table[]? Then remove the IB_QPT_XRC_TGT label in cm_init_qp_rts_attr()?
I think that your interpretation of spec is correct, but why do you want
to remove these attributes? The device ignores them anyway.
Thanks
>
>
> Thxs, Håkon
>
> *1: IBTA Spec Release 1.6 is equal to the XRC Annex in this respect
>
>
next prev parent reply other threads:[~2022-02-07 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 14:55 Seeking clarification on the XRC Annex wrt. a TGT QP having a SQ Haakon Bugge
2022-02-07 18:59 ` Leon Romanovsky [this message]
2022-02-08 10:53 ` Haakon Bugge
2022-02-08 12:07 ` Leon Romanovsky
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=YgFsDXH5XdEBOT/O@unreal \
--to=leon@kernel.org \
--cc=haakon.bugge@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox