From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Venkat Venkatsubra
<venkat.x.venkatsubra-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Michael Nowak
<michael.nowak-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
"Sharp,
Robert O"
<robert.o.sharp-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: rdma_connect() timeout question
Date: Thu, 16 Aug 2012 14:57:18 -0500 [thread overview]
Message-ID: <502D509E.6000403@opengridcomputing.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A8237346A899E6-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 8/16/2012 2:40 PM, Hefty, Sean wrote:
>> Is there a way to tune rdma_connect() timeout to a lower value ?
> I don't believe so.
>
> You could abort the connection by destroying the id after a specified amount of time had expired.
>
>> Can cma_response_timeout and CMA_MAX_CM_RETRIES be made tunables ?
>> Even better would have been if the caller (RDS in this case) could have
>> passed them as connection setup parameters. ;-)
>> That way we don't have to disturb the setting for non-RDS traffic.
> A per rdma_cm_id option for this makes sense to me.
>
> iWarp developers, would timeout/retry values be usable for iwarp?
I think this would be useful for the iwarp side too. Not sure yet
exactly how it would apply for cxgb3/4 though...
--
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
prev parent reply other threads:[~2012-08-16 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 19:01 rdma_connect() timeout question Venkat Venkatsubra
[not found] ` <502D43A4.1090708-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2012-08-16 19:40 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237346A899E6-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-08-16 19:57 ` Steve Wise [this message]
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=502D509E.6000403@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michael.nowak-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=robert.o.sharp-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=venkat.x.venkatsubra-QHcLZuEGTsvQT0dZR+AlfA@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;
as well as URLs for NNTP newsgroup(s).