CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS: default tagged command queue depth

General informations

The Linux kernel configuration item CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS has multiple definitions:

default tagged command queue depth found in drivers/scsi/Kconfig

The configuration item CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS:

• prompt: default tagged command queue depth
• type: int
• depends on: CONFIG_SCSI_ZALON
• defined in drivers/scsi/Kconfig
• found in Linux kernels: 2.5.45–2.5.73, 2.6.18–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.8, 6.9-rc+HEAD

Help text

"Tagged command queuing" is a feature of SCSI-2 which improves performance: the host adapter can send several SCSI commands to a device's queue even if previous commands haven't finished yet. Because the device is intelligent, it can optimize its operations (like head positioning) based on its own request queue. Some SCSI devices don't implement this properly; if you want to disable this feature, enter 0 or 1 here (it doesn't matter which).

The default value is 8 and should be supported by most hard disks. This value can be overridden from the boot command line using the 'tags' option as follows (example): 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to 4, set queue depth to 16 for target 2 and target 3 on controller 0 and set queue depth to 10 for target 0 / lun 2 on controller 1.

The normal answer therefore is to go with the default 8 and to use a boot command line option for devices that need to use a different command queue depth.

There is no safe option other than using good SCSI devices.

default tagged command queue depth found in drivers/scsi/Kconfig

The configuration item CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS:

• prompt: default tagged command queue depth
• type: int
• depends on: CONFIG_SCSI_ZALON || CONFIG_SCSI_NCR_Q720
• defined in drivers/scsi/Kconfig
• found in Linux kernels: 2.5.74–2.5.75, 2.6.0–2.6.17

Help text

"Tagged command queuing" is a feature of SCSI-2 which improves performance: the host adapter can send several SCSI commands to a device's queue even if previous commands haven't finished yet. Because the device is intelligent, it can optimize its operations (like head positioning) based on its own request queue. Some SCSI devices don't implement this properly; if you want to disable this feature, enter 0 or 1 here (it doesn't matter which).

The default value is 8 and should be supported by most hard disks. This value can be overridden from the boot command line using the 'tags' option as follows (example): 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to 4, set queue depth to 16 for target 2 and target 3 on controller 0 and set queue depth to 10 for target 0 / lun 2 on controller 1.

The normal answer therefore is to go with the default 8 and to use a boot command line option for devices that need to use a different command queue depth.

There is no safe option other than using good SCSI devices.

default tagged command queue depth found in arch/sparc64/Kconfig

The configuration item CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS:

• prompt: default tagged command queue depth
• type: int
• depends on: CONFIG_PCI && CONFIG_SCSI_SYM53C8XX_2 != CONFIG_y && ( CONFIG_SCSI_NCR53C8XX || CONFIG_SCSI_SYM53C8XX )
• defined in arch/sparc64/Kconfig
• found in Linux kernels: 2.5.45–2.5.72

Help text

"Tagged command queuing" is a feature of SCSI-2 which improves performance: the host adapter can send several SCSI commands to a device's queue even if previous commands haven't finished yet. Because the device is intelligent, it can optimize its operations (like head positioning) based on its own request queue. Some SCSI devices don't implement this properly; if you want to disable this feature, enter 0 or 1 here (it doesn't matter which).

The default value is 8 and should be supported by most hard disks. This value can be overridden from the boot command line using the 'tags' option as follows (example): 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to 4, set queue depth to 16 for target 2 and target 3 on controller 0 and set queue depth to 10 for target 0 / lun 2 on controller 1.

The normal answer therefore is to go with the default 8 and to use a boot command line option for devices that need to use a different command queue depth.

There is no safe option other than using good SCSI devices.

default tagged command queue depth found in arch/parisc/Kconfig

The configuration item CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS:

• prompt: default tagged command queue depth
• type: int
• depends on: CONFIG_SCSI_ZALON || CONFIG_SCSI_SYM53C8XX
• defined in arch/parisc/Kconfig
• found in Linux kernels: 2.5.45

Help text

"Tagged command queuing" is a feature of SCSI-2 which improves performance: the host adapter can send several SCSI commands to a device's queue even if previous commands haven't finished yet. Because the device is intelligent, it can optimize its operations (like head positioning) based on its own request queue. Some SCSI devices don't implement this properly; if you want to disable this feature, enter 0 or 1 here (it doesn't matter which).

The default value is 8 and should be supported by most hard disks. This value can be overridden from the boot command line using the 'tags' option as follows (example): 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to 4, set queue depth to 16 for target 2 and target 3 on controller 0 and set queue depth to 10 for target 0 / lun 2 on controller 1.

The normal answer therefore is to go with the default 8 and to use a boot command line option for devices that need to use a different command queue depth.

There is no safe option other than using good SCSI devices.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: