CONFIG_SD_EXTRA_DEVS: Maximum number of SCSI disks that can be loaded as modules

General informations

The Linux kernel configuration item CONFIG_SD_EXTRA_DEVS has multiple definitions:

Maximum number of SCSI disks that can be loaded as modules found in arch/um/Kconfig.scsi

The configuration item CONFIG_SD_EXTRA_DEVS:

• prompt: Maximum number of SCSI disks that can be loaded as modules
• type: int
• depends on: CONFIG_BLK_DEV_SD
• defined in arch/um/Kconfig.scsi
• found in Linux kernels: 2.6.14–2.6.21

Help text

(none)

Maximum number of SCSI disks that can be loaded as modules found in arch/um/Kconfig_scsi

The configuration item CONFIG_SD_EXTRA_DEVS:

• prompt: Maximum number of SCSI disks that can be loaded as modules
• type: int
• depends on: CONFIG_BLK_DEV_SD
• defined in arch/um/Kconfig_scsi
• found in Linux kernels: 2.5.45–2.5.75, 2.6.0–2.6.13

Help text

(none)

Maximum number of SCSI disks that can be loaded as modules found in arch/sparc64/Kconfig

The configuration item CONFIG_SD_EXTRA_DEVS:

• prompt: Maximum number of SCSI disks that can be loaded as modules
• type: int
• depends on: CONFIG_BLK_DEV_SD
• defined in arch/sparc64/Kconfig
• found in Linux kernels: 2.5.45–2.5.72

Help text

This controls the amount of additional space allocated in tables for drivers that are loaded as modules after the kernel is booted. In the event that the SCSI core itself was loaded as a module, this value is the number of additional disks that can be loaded after the first host driver is loaded.

Admittedly this isn't pretty, but there are tons of race conditions involved with resizing the internal arrays on the fly. Someday this flag will go away, and everything will work automatically.

If you don't understand what's going on, go with the default.

Maximum number of SCSI disks that can be loaded as modules found in arch/sparc/Kconfig

The configuration item CONFIG_SD_EXTRA_DEVS:

• prompt: Maximum number of SCSI disks that can be loaded as modules
• type: int
• depends on: CONFIG_BLK_DEV_SD
• defined in arch/sparc/Kconfig
• found in Linux kernels: 2.5.45–2.5.72

Help text

This controls the amount of additional space allocated in tables for drivers that are loaded as modules after the kernel is booted. In the event that the SCSI core itself was loaded as a module, this value is the number of additional disks that can be loaded after the first host driver is loaded.

Admittedly this isn't pretty, but there are tons of race conditions involved with resizing the internal arrays on the fly. Someday this flag will go away, and everything will work automatically.

If you don't understand what's going on, go with the default.

Maximum number of SCSI disks that can be loaded as modules found in arch/m68k/Kconfig

The configuration item CONFIG_SD_EXTRA_DEVS:

• prompt: Maximum number of SCSI disks that can be loaded as modules
• type: int
• depends on: CONFIG_BLK_DEV_SD
• defined in arch/m68k/Kconfig
• found in Linux kernels: 2.5.45–2.5.72

Help text

This controls the amount of additional space allocated in tables for drivers that are loaded as modules after the kernel is booted. In the event that the SCSI core itself was loaded as a module, this value is the number of additional disks that can be loaded after the first host driver is loaded.

Admittedly this isn't pretty, but there are tons of race conditions involved with resizing the internal arrays on the fly. Someday this flag will go away, and everything will work automatically.

If you don't understand what's going on, go with the default.

Maximum number of SCSI disks that can be loaded as modules found in arch/parisc/Kconfig

The configuration item CONFIG_SD_EXTRA_DEVS:

• prompt: Maximum number of SCSI disks that can be loaded as modules
• type: int
• depends on: CONFIG_BLK_DEV_SD
• defined in arch/parisc/Kconfig
• found in Linux kernels: 2.5.45

Help text

This controls the amount of additional space allocated in tables for drivers that are loaded as modules after the kernel is booted. In the event that the SCSI core itself was loaded as a module, this value is the number of additional disks that can be loaded after the first host driver is loaded.

Admittedly this isn't pretty, but there are tons of race conditions involved with resizing the internal arrays on the fly. Someday this flag will go away, and everything will work automatically.

If you don't understand what's going on, go with the default.

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: