On Sat, 2005-10-22 at 11:58 +0100, Christoph Hellwig wrote: > On Sat, Oct 22, 2005 at 12:42:27PM +0200, Stefan Richter wrote: > > A. Post mock-ups and pseudo code about how to change the core, discuss. > > B. Set up a scsi-cleanup tree. In this tree, > > 1. renovate the core (thereby break all command set drivers and > > all transport subsystems), > > No way. Doing things from scatch is a really bad idea. See how far we came > with Linux 2.6 scsi vs 2.4 scsi without throwing everything away and break the > world. Please submit changes to fix _one_ thing at a time and fix all users. > Repeat until done or you don't care anymore. It is a mistake to think that you can not do a big rework and keep SCSI sub-system stable. You just have to make sure the OLD way is supported for as log as it is needed. E.g. before moving in the RIGHT direction and weeding out parallel SCSI atavism from the common SCSI layer (or should I say SAM, to please Luben) you can insert "generic" transport layer at the bottom (just like Luben inserted his SAS) and use it to keep all currently supported drivers stable. SCSI mid-layer can be reworked in any number of steps, even in one step, because is not a big thing, it is just 11k lines plus 4k of recently added transport modules. > - > : send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
