> Solaris kernel modules such as NFS use kernel TLI implementation to > create a TCP connection to remote servers. The kernel TLI is a subset > of larger user level TLI interface. However there is no documentation > for kernel programmers. I understand that it is most likely > contract-private interface.
Yes, the KTLI/TPI interface is intentionally undocumented. We'd like to remove it someday. > For someone writing a new loadable kernel module , is TLI the > recommended interface ? Are there any efforts to document it ? Are > there any known issues that programmer should be aware of ? AFAIK, there isn't a recommend interface at this time. There are a set of so*() routines in socksyscalls.c that roughly mirror the BSD sockets API (e.g., soaccept(), sobind(), ...), and are available for use inside the ON consolidation. Sun Cluster (which is not part of ON) also has a contract to use these interfaces. Accordingly, if you needed to use these in an unbundled product, you'd need to get a contract to do so safely. That said, I'd much prefer to see work go into creating a kernel sockets API that could be made part of the Solaris DDI. It would certainly make a nice OpenSolaris project :-) -- meem _______________________________________________ networking-discuss mailing list [email protected]
