On Fri, Feb 05, 2010 at 11:35:28AM -0800, [email protected] wrote: > >One more thought -- I realized that even separating out "functionality" > >for driver names will fly in the face of current emerging trends towards > >"convergence". For example, new hardware from emulex, qlogic, and others > >support HBA functionality *and* NIC functionality on the same part. > >ConnectX parts from Mellanox can be used as a 10GbE, a fibre-channel HBA, > >or an Infiniband HCA. Where do you put these? driver/storage/... > >driver/network/.... driver/infiniband/... ?!? > > Yes, there was one such package at the moment. I believe providing > some sort of functional boundary is still useful in the namespace. As > more such drivers are integrated, we can certainly carve out additional > namespace, or rely on some sort of ordering (namely if a driver > delivers both HBA and NIC functionality, put it under storage.)
What's the difference between storage and network controllers anyways? ;^) Well, seriously, it's all the same now. You can use ib/ofed/... for messaging and Ethernet for storage. My recommendation is to put all of these under network, not storage. /storage should reserved for drivers of actual storage-related devices that are not network controllers. Nico -- _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
