> Maybe(?) there is another approach...  Please forgive my naivet�.
> The real problem is that fact that anything not serviced by the boot SCSI
> driver is subject to the SD_EXTRA_DEVS limit.  For example, if my box has
> an
> Adaptec on the motherboard (w/ boot device attached), anything on the
> Symbios/Qlogic/XX adapters would be subject to SD_EXTRA_DEVS.
>
> What kind of code gymnastics would be required to scan _all_ the SCSI
> drivers installed before saying "this is all the devices we found"?
> Extend the initial scan to include the buses attached to additional
> adapters.

    Let me study the code a bit - I believe it would be a more minor
re-arrangement to attach the devices after all of the compiled in drivers
are scanned, but I won't commit to that without looking.  I would feel more
comfortable doing this for 2.3 - it would be Alan's call what is safe enough
to go in 2.2, and until I have a rough idea of what changes are needed it
would be hard to make a call on this.

> With that kind of function, users would still have to reboot to config all
> devices, but its a start.  Then SD_EXTRA_DEVS would apply only to those
> "extra" devices added between reboots...
>
> In any event, just about any number you choose is going to be too small as
> the momentum builds towards FC and Linux clusters.  Personally I'd like to
> boot off of my internal SCSI bus and be able to access at least one full
> FC-AL, but SD_EXTRA_DEVS = 128 would probably cause memory prices to rise.
>
> Another blue sky idea:  Could SD_EXTRA_DEVS be added SCSI lilo bootparms?
> Users already have to add a 'max_scsi_luns' statement to lilo.conf to
> access serious storage.

    Yes, but in the long term I would like to eliminate SD_EXTRA_DEVS
completely, at which time the point becomes moot.  I suppose it would make
sense to allow a boot-time override, as this would be a relatively safe
change for a 2.2 series kernel.  In fact the elimination of SD_EXTRA_DEVS
probably won't even happen for 2.4, so a boot-time override would make sense
for 2.3/2.4 as well.

-Eric



-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]

Reply via email to