[ofa-general][PATCH 0/4] SRP fail-over faster

[ofa-general][PATCH 0/4] SRP fail-over faster

[Vu Pham]

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: [ofa-general][PATCH 0/4] SRP fail-over faster.eml --]
[-- Type: message/rfc822, Size: 1910 bytes --]

From: Vu Pham <vuhuong-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: OF General <general-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>, Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Subject: [ofa-general][PATCH 0/4] SRP fail-over faster
Date: Mon, 12 Oct 2009 15:46:30 -0700
Message-ID: <4AD3B1C6.9050400-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

Testing srp fail-over with dm-multipath/multipathd/srp_daemon, the 
current srp implementation will take average 3-5 minutes to complete the 
error recovery before return DID_BAD_TARGET so that dm-multipath can 
switch to other paths. During this error recovery, there is no I/O 
happening (old and new I/Os)

The following patches attempt to help srp fail-over faster and 
controllable. It introduces srp_dev_loss_tmo module parameter, so that, 
srp will fail-over after srp_dev_loss_tmo expired.The minimum value for 
srp_dev_loss_tmo is 60 seconds.

Patch 1/4: recreate qp and cq at reconnect instead of reuse them
Patch 2/4: disconnect request without wait.
Patch 3/4: introducing srp_dev_loss_tmo, creating a timer on qp_error event.
Patch 4/4: setting up async event handler to handle local port up/down 
events

The fail-over will be more accurate on local port up/down events (ie. 
someone pull the cable connect local port to switch), it is less 
accurate on target port up/down events (ie. someone pull the cable 
connect target port to switch)

To be accurate on target port up/down events, it requires to change 
srp_daemon to catch the event of IB target port joining/leaving the 
fabric, then pass these event down to srp driver, srp driver need to 
implement entry points to receive these events and act upon them. These 
are missed on this attempt

thanks,
-vu