Skip to contentSkip to conversation

scsi_wait_scan Kconfig option

PATCH Nick Warne 2 participants 3 messages Dec 7, 2007 SCSI

lore
Share & tools
lore

Nick Warne

author
#0 lore raw

Hi all,

Please see below.

Nick

Begin forwarded message:

Date: Fri, 7 Dec 2007 19:12:42 +0000
From: Nick Warne <[email protected]>
To: [email protected]
Subject: scsi_wait_scan Kconfig option

Hi all,

I am bringing this up again - primarily as I forgot about it after patching my build tree ages ago:

http://lkml.org/lkml/2007/10/27/68

Today I built and installed git for the first time and cloned Linus' tree (very trick!).

I try not to build a modular kernel, but only have modules ON due to nVidia (sigh). So I was semi-surprised when I saw the scsi_wait_scan module being built again, yet NO WHERE in menuconfig is it present to turn OFF. Even if I hand edit .config, make puts it back again...

.config
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
# CONFIG_SCSI_PROC_FS is not set

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs #
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set CONFIG_SCSI_WAIT_SCAN=m

I have attached my patch again :-)

Nick

Signature · 4 lines
Free Software Foundation Associate Member 5508

-- 
Free Software Foundation Associate Member 5508
drivers/scsi/Kconfig renamed from drivers/scsi/Kconfig_old +8 -1
@@ -248,10 +248,17 @@
 	  or async on the kernel's command line.
 
 config SCSI_WAIT_SCAN
-	tristate
+	tristate "Wait for SCSI scan completion"
 	default m
 	depends on SCSI
 	depends on MODULES
+	help
+	  The SCSI subsystem can probe for devices while the rest of the
+	  system continues booting, and even probe devices on different
+	  busses in parallel, leading to a significant speed-up.
+
+	  You can load the scsi_wait_scan module to ensure that all scans
+	  have completed.
 
 menu "SCSI Transports"
 	depends on SCSI
#1 lore raw
Quoted 4 lines · Nick Warne

I try not to build a modular kernel, but only have modules ON due to nVidia (sigh). So I was semi-surprised when I saw the scsi_wait_scan module being built again, yet NO WHERE in menuconfig is it present to turn OFF. Even if I hand edit .config, make puts it back again...

You have modules on ... which means you might decide to load a scsi driver as a module. Maybe one that isn't part of the source tree. The scsi_wait_scan module is only 1500 bytes. Apart from a sense of ideological purity (odd in someone who chooses to use nVidia rather than, say, nv or nouveau), this really isn't a problem.

Signature · 4 lines
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
author
#2 lore raw

Hi Matthew,

Quoted 7 lines · On Fri, 7 Dec 2007 12:47:56 -0700 Matthew Wilcox <[email protected]> wrote:
Quoted 5 lines · Nick Warne

I try not to build a modular kernel, but only have modules ON due to nVidia (sigh). So I was semi-surprised when I saw the scsi_wait_scan module being built again, yet NO WHERE in menuconfig is it present to turn OFF. Even if I hand edit .config, make puts it back again...

Quoted 5 lines

You have modules on ... which means you might decide to load a scsi driver as a module. Maybe one that isn't part of the source tree. The scsi_wait_scan module is only 1500 bytes. Apart from a sense of ideological purity (odd in someone who chooses to use nVidia rather than, say, nv or nouveau), this really isn't a problem.

Alas the card I have isn't supported, but that debate isn't for here.

OK, I only have SCSI set for USB storage etc. I find it strange that this one and only option in the whole of Kconfig builds a module, and yet, even though I know I will never need it, I can't stop it.

Surely if people build their own kernels, they should know (and) be allowed to configure such options?

Nick

Signature · 1 line
Free Software Foundation Associate Member 5508