Thread (1 message) 1 message, 1 author, 2012-09-20

Re: how to preserve QP over HA events for librdmacm applications

From: Pradeep Satyanarayana <hidden>
Date: 2012-09-20 17:37:52

On 09/19/2012 11:14 AM, Atchley, Scott wrote:
On Sep 19, 2012, at 1:05 PM, "Hefty, Sean"[off-list ref]  wrote:
quoted
quoted
I too would be interested in bringing a QP from error back to a usable state. I
have been debating whether to reconnect using the current RDMA calls versus
trying to transition the existing RC QP.

I assumed to transition the existing QP that I would need to open a socket to
coordinate the two sides. Is that correct?

If I were instead to use rdma_connect(), does it require a new CM id or just a
new QP within the same id?
What if you say pre-created a second (fail over) QP for HA purposes all 
under the covers of a single socket? And both QPs were connected before 
the failure. Not sure if that would work with the same CM id though. If 
not, we will need to rdma_connect() the second QP after failure.

By having a second QP and bound to say a different port/device, one 
could survive not just link up/down events, but device failures too. 
Would that be more generic?

Thanks
Pradeep

--
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help