Leaked source code of windows server 2003
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
Configuring Power Paramters: ----------------------------
Scsiport allows adapters to configure some power settings.
NeedsSystemShutdownNotification: DWORD If nonzero, this value tells scsiport that the adapter needs to have its AdapterControl routine called when a system shutdown occurs. See the section on request sense parameters below for the location of this key.
Configuring Tunable Performance Parameters: -------------------------------------------
Scsiport supports the following configurable perfomance parameters:
RemainInReducedMaxQueueState: DWORD If set, this value indicates the number of seconds a logical unit will remain in a degraded performance state in which its MaxQueueDepth has been reduced due to one or more requests failed with QUEUE FULL status. This value is read from ScsiPort's DeviceParameters key in the registry. See the section on request sense parameters below for the location of this key.
Configuring Request Sense Parameters: -------------------------------------
Scsiport supports configurable request sense parameters on a per-adapter basis. The following parameters may be configured under the HBA's device entry:
TotalSenseDataBytes: DWORD [18..255] If set, this value designates the size of the buffer Scsiport will allocate for request sense data. If the value is not set, the default size of 18 (0x12) bytes is used.
RequestSenseTimeout: DWORD If set, this value designates the timeout period for REQUEST SENSE commands, in seconds. If the value is not set, the default timeout value of 2 seconds is used.
SenseDataEventClass: STRING This string value is a GUID that identifies a WMI event class. If this value is present, the port driver will generate a WMI event containing the request sense data every time a REQUEST SENSE occurs. The WMI event class must be added into the repository for clients to find it. See the DDK for the ways this can be done. One way is to use the MOF compiler, MOFCOMP... mofcomp -N:root\wmi scsiport.mof
HKLM System CurrentControlSet Enum <bus> <DeviceId> <Device> DeviceParameters ScsiPort DWORD TotalSenseDataBytes=<18..255> DWORD RequestSenseTimeout=<timeout in seconds> DWORD RemainInReducedMaxQueueState=<duration in seconds> DWORD NeedsSystemShutdownNotification=<0|1> STRING SenseDataEventClass={GUID}
Example: HKLM System CurrentControlSet Enum PCI VEN_9004&DEV_6178&SUBSYS_78619004&REV_03 3&1b3e6122&0&5070 DeviceParameters ScsiPort TotalSenseDataBytes=0xff RequestSenseTimeout=0xa RemainInMaxQueueState=0x1e NeedsSystemShutdownNotification=1 SenseDataEventClass={d69fad96-c9a3-4ed0-b98b-47c27feac68c}
Verifier: --------
To enable the scsi verifier, add the following registry entry to the scsiport control entry...
HKLM\system\currentcontrolset\control\scsiport Verifier VerifyLevel = <verifier level>
The following values control verifier behavior... #define SP_DONT_CHK_HW_INITIALIZE_DURATION 0x80000000 #define SP_DONT_CHK_ACTIVE_UNTAGGED_REQUEST 0x40000000 #define SP_DONT_CHK_REQUESTS_ON_RESET 0x20000000
Also, from the debugger, setting SpVrfyLevel=0xffffffff will disable the verifier.
|