Re: Patches for SCSI scanning

[Kurt Garloff <garloff@suse.de>]

[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]

Hi James,

On Sun, Apr 18, 2004 at 06:16:31PM -0500, James Bottomley wrote:
> Erm, Kurt, we already have a module load time parameter for altering
> both blacklist entries and scanning defaults.
> 
> It's dev_flags and default_dev_flags in scsi_devinfo.c
> 
> Could you first explain why you can't use this existing infrastructure?

I've overlooked that possibility.
default_dev_flags obsoletes patch 1 (sparselun and largelun paramters -- 
almost, but max_sparseluns is probably only useful in corner cases), 
and dev_flags obsoletes the patch 6 (llun_blklst).

I'll drop them.

What about the others:
* Patch 2: Drop REPORT_LUN config option and introduce 
  noreportlun and reportlun2 parameters (the latter allowing SCSI-2
  devs to be scanned with REPORT_LUNS).
* Patch 3: Allow host adapters to avoid REPORT_LUNS.
* Patch 4: allow_ghost_devices parameter
* Patch 5: inq_timeout parameter 

If we introduce two more BLIST flags (BLIST_NOREPORTLUN and
BLIST_REPORTLUN2), we can get rid of patch 2 and 3, if we add another one
(BLIST_LUN0ONLINE), we can get rid off 4.

We have 16 bits left, so it should be possible.

If there's consensus to go that way, I can code it up, no problem.
Only patch 5 will remain then ...

Sidenote: We should drop SCSI_FORCELUN and CONFIG_SCSI_MULTI_LUN, otherwise 
people will misconfigure their kernel (such as the HP guy) and start to want 
every multi-lun device listed.

Regards,
-- 
Kurt Garloff                   <kurt@garloff.de>             [Koeln, DE]
Physics:Plasma modeling <garloff@plasimo.phys.tue.nl> [TU Eindhoven, NL]
Linux: SUSE Labs (Head)        <garloff@suse.de>    [SUSE Nuernberg, DE]

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]