summaryrefslogtreecommitdiffstats
path: root/include/scsi
diff options
context:
space:
mode:
authorVasu Dev <vasu.dev@intel.com>2009-11-03 11:48:06 -0800
committerJames Bottomley <James.Bottomley@suse.de>2009-12-04 12:01:10 -0600
commit84c3e1ad08d4be018a95e7a9964bf3dbc8cf8857 (patch)
tree1dcd106bcf8e64afce588f7914a082a21f45e941 /include/scsi
parentc46be11a683acc1ccf86883ea906f171b90ff29a (diff)
downloadop-kernel-dev-84c3e1ad08d4be018a95e7a9964bf3dbc8cf8857.zip
op-kernel-dev-84c3e1ad08d4be018a95e7a9964bf3dbc8cf8857.tar.gz
[SCSI] libfc: adds can_queue ramp up
Adds last_can_queue_ramp_down_time and updates this on every ramp down. If last_can_queue_ramp_down_time is not zero then do ramp up on any IO completion in added fc_fcp_can_queue_ramp_up. Reset last_can_queue_ramp_down_time to zero once can_queue is ramped up to added max_can_queue limit, this is to avoid any more ramp up attempts on subsequent IO completion. The ramp down and up are skipped for FC_CAN_QUEUE_PERIOD to avoid infrequent changes to can_queue, this required keeping track of ramp up time also in last_can_queue_ramp_up_time. Adds code to ramp down can_queue if lp->qfull is set, with added new ramp up code the can_queue will be increased after FC_CAN_QUEUE_PERIOD, therefore it is safe to do ramp down without fsp in this case and will avoid thrash. This required fc_fcp_can_queue_ramp_down locking change so that it can be called with Scsi_Host lock held. Removes si->throttled and fsp state FC_SRB_NOMEM, not needed with added ramp up code. Signed-off-by: Vasu Dev <vasu.dev@intel.com> Signed-off-by: Robert Love <robert.w.love@intel.com> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'include/scsi')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud