
Table 3: LPFC.conf Parameters (Continued)
Property Name | Scope | Default | Min | Max | Dynamic | Comments |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Controller | 1 | 0 | 128 | Yes | Amount to increment LUN | |
inc | Specific |
|
|
|
| queue depth each time. This |
|
|
|
|
|
| driver property causes the |
|
|
|
|
|
| LPFC driver to decrement a |
|
|
|
|
|
| LUN’s queue depth, if a queue |
|
|
|
|
|
| full condition is received from |
|
|
|
|
|
| the target. The queue depth |
|
|
|
|
|
| will be decremented down to a |
|
|
|
|
|
| minimum of 1. The variables |
|
|
|
|
|
| |
|
|
|
|
|
| |
|
|
|
|
|
| used to restore the queue |
|
|
|
|
|
| depth back to the original. The |
|
|
|
|
|
| |
|
|
|
|
|
| property defines a time, in |
|
|
|
|
|
| seconds, that is used to tell |
|
|
|
|
|
| when to increase the current |
|
|
|
|
|
| queue depth. If the current |
|
|
|
|
|
| queue depth isn't equal to the |
|
|
|
|
|
| |
|
|
|
|
|
| driver stop_send_io flag is |
|
|
|
|
|
| equal to 0 for that device, |
|
|
|
|
|
| increment the current queue |
|
|
|
|
|
| depth by |
|
|
|
|
|
| (don't exceed the |
|
|
|
|
|
| depth). So, if both driver |
|
|
|
|
|
| properties are set to 1, then |
|
|
|
|
|
| the driver increments the |
|
|
|
|
|
| current queue depth once per |
|
|
|
|
|
| second until it hits the lun- |
|
|
|
|
|
| |
|
|
|
|
|
| way to restore the queue |
|
|
|
|
|
| depth (besides rebooting), |
|
|
|
|
|
| back to the original LUN |
|
|
|
|
|
| throttle, is by running the |
|
|
|
|
|
| command |
|
|
|
|
|
| /opt/lpfc/resetqdepth X. This |
|
|
|
|
|
| will restore the LUN throttle of |
|
|
|
|
|
| all LUNs for HBA X back to |
|
|
|
|
|
| the original value. |
|
|
|
|
|
|
|
The HBAnyware Utility User Manual | Page 64 |