--- Jeff Garzik <jgarzik@xxxxxxxxx> wrote: > Invalid example. All of the methods listed -- request_queue, netlink, > chrdev, sysfs, ioctl -- will work just fine when the root filesystem is > on the far side of a SAS expander. These are just methods of > communication, nothing more. Jeff, why don't you listen from time to time to people who work with the technology on a daily basis who have experience with it, who have _insight_ of the technology? Such insight gives them great intuition when it comes to design, among other things. > In your example -- userspace discovery required before root filesystem > can be found -- a program running from initrd/initramfs would create an > SMP device node, open it, and then proceed with the discovery and SMP is part of the protocol, of what the device (PCI) implements. It is always there, just like phys. You do not need to create it from user space. It will be there for a user process to use, via say SDI. SDI provides this as part of the controller. Read the SDI spec. Insight of the whole architecture is irreplacable to create good design. > configuration process, which in turn creates the device nodes necessary > to mount the root filesystem. Also note that everyone does domain discovery in the kernel/FW and not only for SAS but for other domains (even non-SCSI). While domain discovery is in the kernel/FW, _control_ of the domain is given to user space, via say SDI -- everyone agrees on this. 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
