ibmvscsi: dynamic request_limit and device restart
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v1 Latest posting 2/20 of 2 patches 0 repliesNew
- v1 posting 1/22 patches 2 repliesSuperseded
Patches in v1 posting 2/2 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2][resend] ibmvscsi: dynamic request_limit and device restart
James,
Resending these patches for inclusion in your tree.
There are two fixes for the ibmvscsi client driver in this set.
- Dynamic request_limit
The request_limit for the driver was not properly reflecting the value on the server side and could cause can_queue to be set to improper values (-1). The patch corrects this so that request_limit mirrors the value on the server and sets can_queue appropriately.
- Device restart
When a drive was removed from the server and then re-added the client would not be able to use that device. The device would return a unit attention and then not ready. By adding a slave_configure function we can set the "allow_restart" flag for all disk devices. Now devices will resume functioning when they are re-added to the server.
---