> But worth mentioning - I can fix this the next time I am in the code,
> and we won't have to worry about it any longer. No point in allowing these
> silly little things to stand in the way of progress.
Can you do this before 3.4, please?
>
> > In terms of adding extra devs- this is a quantity only pertinent
> > for allocating extra space for loadable HBA rescans- this doesn't have
> > anything to do with boot time probing with static linking, or if it does,
> you
> > can always change the SD_EXTRA_DEVS to something reasonable (like 512).
>
> We still have an effective limit of 128 disks. 8 majors * 16
> disks/major.
>
> Now that devfs is in, I am wondering whether it would make sense to
> allow the disk driver to dynamically allocate as many majors as it needs
> above and beyond the 8 majors. All of the hardcoded assumptions about major
> numbers should be gone from ll_rw_blk.c. In there would be the nasty problem
> of somehow getting the /dev tree - with devfs, that becomes a non-issue as
> the /dev entries are automatically created.
[ he hops up and down chanting yes yes yes yes ! !!! ]
>
> There is still a limit of 256 majors * 16 disks/major or 4096 disks (an
> over-estimate as some majors are unavailable). We won't worry about that
> for now... :-).
>
Well, maybe we should. It's not so much that 4096 is large, very soon it won't
be with a fabric- it's whether or not the lack of anything larger will force a
fabric midlayer to have to do a pick-n-choose policy for binding disks to ids.
-matt
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
