From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: DREQ timeout for rdma-cm consumers Date: Thu, 28 Jan 2010 15:03:59 +0200 Message-ID: <4B618B3F.9030803@voltaire.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Sean Hefty Cc: linux-rdma List-Id: linux-rdma@vger.kernel.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 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 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