From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: initiator depth and responder resources in a connect request.
Date: Mon, 14 Mar 2011 10:34:00 -0500 [thread overview]
Message-ID: <4D7E3568.7010406@opengridcomputing.com> (raw)
In-Reply-To: <CF9C39F99A89134C9CF9C4CCB68B8DDF25CCAC5612-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 03/14/2011 10:28 AM, Hefty, Sean wrote:
>> Dumb question: What exactly do the rdma_conn_param fields initiator_depth
>> and responder_resources mean in an incoming
>> connection request? Does it mean the peer's values for these two
>> resources, or is responder_resources set to match the
>> peer's initiator_depth and initiator_depth set to match the peer's
>> responder_resources? IE Are they swapped so the app
>> can turn around and use them in the rdma_accept()?
> The values are swapped. See the man page for rdma_get_cm_event and let me know if it's not clear.
Thanks. Yes. That man page is clear.
I think the rdma_accept() page has a bug though:
----
responder_resources
The maximum number of outstanding RDMA read and atomic opera-
tions that the local side will accept from the remote side.
Applies only to RDMA_PS_TCP. This value must be less than or
equal to the local RDMA device attribute max_qp_rd_atom and the
responder_resources value reported in the connect request event.
----
"and the responder_resources value" should be "and greater than or equal to the responder_resources value".
Steve.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-14 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 14:36 initiator depth and responder resources in a connect request Steve Wise
[not found] ` <4D7E27E4.7060606-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2011-03-14 15:28 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25CCAC5612-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-03-14 15:34 ` Steve Wise [this message]
[not found] ` <4D7E3568.7010406-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2011-03-14 21:33 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25CCB39DF3-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-03-14 21:35 ` Steve Wise
[not found] ` <4D7E8A25.8010701-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2011-03-14 21:40 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25CCB39E12-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-03-14 21:57 ` Steve Wise
[not found] ` <4D7E8F60.7030006-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2011-03-14 22:12 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25CCB39EAF-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-03-14 22:19 ` Steve Wise
2011-03-14 22:14 ` 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=4D7E3568.7010406@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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