public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: DREQ timeout for rdma-cm consumers
Date: Thu, 28 Jan 2010 15:03:59 +0200	[thread overview]
Message-ID: <4B618B3F.9030803@voltaire.com> (raw)
In-Reply-To: <F766FA8B1AD74F0E98EF28981448A4CF-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>

Sean Hefty wrote:
> I believe that the IB timeout of 20 is about 4 seconds.  If the packet lifetime is 1 second, then each try will take 6 seconds to timeout.  For 15 retries, this is close to 100 seconds.  
okay, thanks for explaining this.

> You should be able to destroy the rdma_cm_id at anytime
I understand that, however, currently the code I am working with (iser) 
wait to get both flushes on all the posted work requests AND disconnect 
or address-change event to mark the <rdmacm id, qp> couple as 
disconnected, clear it up and signal higher level to reconnect. I'll 
have to look what is the way to go for fast reconnection, maybe connect 
a new <id, qp> couple before the current one is totally 
flushed/disconnected. Also, destroying the ID doesn't remove the qpn 
from the IB CM timewait database, correct? hence if I don't wait long 
enough and the driver/hw reuses the qpn short enough to hit the IB CM 
stale connection/etc logic, I will not be able to reconnect, I guess.

Or.
--
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

  parent reply	other threads:[~2010-01-28 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 16:16 DREQ timeout for rdma-cm consumers Or Gerlitz
     [not found] ` <Pine.LNX.4.64.1001261749260.13804-aDiYczhfhVLdX2U7gxhm1tBPR1lH4CV8@public.gmane.org>
2010-01-28  5:22   ` Sean Hefty
     [not found]     ` <F766FA8B1AD74F0E98EF28981448A4CF-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-01-28 13:03       ` Or Gerlitz [this message]
     [not found]         ` <4B618B3F.9030803-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2010-01-28 17:41           ` Sean Hefty

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=4B618B3F.9030803@voltaire.com \
    --to=ogerlitz-smomgflxvozwk0htik3j/w@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