On 09/29/05 11:20, Jeff Garzik wrote: >>Arjan, I'll be your best friend here: >>Never say this in public or in an intervew. > > > It's hard-earned experience. We constantly have to teach hardware > vendors how to write good drivers. I'm sure you have. Hardware vendors are lost without Jeff, James Bottomley and Christoph. You see, it is because of your _enormous_ ego as shown above, that the code is being blocked. > At some point you have to step away from the spec, and ask yourself what > makes sense for Linux. I'm sure -- flush interoperability down the drain. > I've already had to poke T10 when they put silly > things in the SAT spec. Surely they are lost without you. > As a tangent, I already have a design for a Linux filesystem that makes > use of SCSI object-based storage (to James's horror, no doubt :)). It's > a fun thing to ponder. Ok, so the way I see it you want to show who has got the bigger balls? Jeff, I have *worked* on a Linux OBD-based filesystem. Are you going to stop this self-gratifying stuff? >>Hardware folks needs to work with software folks and >>software folks need to work with hardware folks. > > Certainly. The historical disconnect is where hardware vendors tend to > presume They Know Best, when in reality it needs to be an equal > tradeoff. Hardware vendors must admit they don't know Linux, and Linux > developers must admit that hardware vendors know their own hardware > better than anyone else. Reflection of above: The historical disconnect is where "the community" tend to presume They Know Best, when in reality it needs to be an equal tradeoff. "The community" must admit they don't know hardware, and hardware developers must admit that "the community" know their own code better than anyone else. Jeff, if you had started looking at the design and firmware of any new SCSI storage chip, you'd see how incredibly similar it is to the transport it defines, and thus to SAM, since the transport itself has to comply with SAM for interoperability (TMF and all). Linux SCSI does _not_ need to do "its own thing". There are perfectly well defined specs, telling you how things are conceptually _and_ in the physical world. In order to control those objects, you need to represent them internally (you can learn this either in neuroscience class or in OOD & OOP comp sci classes) as you can see has been done in the SAS Transport Layer code. So if you want _better control_, higher quality you need to invent _your own_ stuff as _little as possible_ and represent things as they are. Luben - : 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
