Jeff Garzik wrote: > Caitlin Bestler wrote: >> Jeff Garzik wrote: >>> Caitlin Bestler wrote: >>>> But hardware iSCSI implementations, which already exist, do not >>>> work through normal sockets. > >>> No, they work through normal SCSI stack... > >> Correct. >> >> But they then interface to the network using none of the network >> stack. The normal SCSI stack does not control that it any way. > > Correct. And the network stack is completely unaware of > whatever IP addresses, ARP tables, routing tables, etc. it is using. > > >> NFS over RDMA is part of the file system. That doesn't change the >> fact that it's use of IP Addresses needs to be co-ordinated with the >> network stack, and indeed that address based authentication >> *assumes* that this is the case. (and yes, there are preferable >> means of authentication, but authenticating based on IP address is >> already supported). > > Sounds quite broken to me. > > >> But back on the main point, if implementing SCSI services over a >> TCP connection is acceptable even though it does not use a kernel >> socket, why would it not be acceptable to implement RDMA services >> over a TCP connection without using a kernel socket? > > Because SCSI doesn't force nasty hooks into the net stack to > allow for > sharing of resources with a proprietary black box of unknown quality. > > Jeff
RDMA can also solve all of these problems on its own. Complete with giving the network administrator *no* conventional controls over the IP address being used for RDMA services. That means no standard ability to monitor connections, no standard ability to control which connections are made with whom. That is better? You seem to be practically demanding that RDMA build an entire parallel stack. Worse, that *each* RDMA vendor build an entire parallel stack. Open source being what it is, that is not terribly difficult. But exactly how does this benefit Linux users? The proposed subscriptions are not about sharing *resources*, they share *information* with device drivers. The quality of each RDMA device driver will be just as known as for a SCSI driver, an InfiniBand HCA driver, a graphics driver or a plain Ethernet driver. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
