Return to BSD News archive
Xref: sserve comp.unix.internals:7607 comp.unix.solaris:21720 comp.unix.sys5.r4:8201 comp.unix.bsd:14706 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!nsslsun.nssl.uoknor.edu!news.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!henson!reuter.cse.ogi.edu!hp-cv!hp-pcd!sdd.hp.com!spool.mu.edu!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!yeshua.marcam.com!charnel.ecst.csuchico.edu!olivea!koriel!news2me.EBay.Sun.COM!engnews2.Eng.Sun.COM!cthulhu!denny From: denny@eng.sun.com (Denton Gentry) Newsgroups: comp.unix.internals,comp.unix.solaris,comp.unix.sys5.r4,comp.unix.bsd Subject: Re: DLPI Vs BSD Sockets Vs Sys V TLI Date: 25 Aug 1994 20:46:48 GMT Organization: Sun Microsystems Computer Corp Lines: 12 Distribution: world Message-ID: <33ivvo$mr2@engnews2.Eng.Sun.COM> References: <33iecq$leg@crl2.crl.com> Reply-To: denny@eng.sun.com NNTP-Posting-Host: maverick.eng.sun.com In article leg@crl2.crl.com, cgi@crl.com (Paul Smith) writes: >3rd, TLI is the layer 4/ transport layer interface stream API. Functionally >equivalent to Berkeley Sockets API. But the sockets API on SVR4.* is >implimented as a library translation layer into TLI calls. SLOW! Or >more accurately, slower than calling TLI direcly. This is of course >using either TCP or UDP over IP over DLPI. So, DLPI is the fastest, or >closest to the hardware you can get short of writting your own driver... This is incorrect for Solaris. The socket calls and TLI calls both manipulate the stream head. Socket calls do not get translated to TLI calls in a library function, sockets and TLI both manipulate the stream head. In most cases the source code for equivalent socket routines and TLI routines are remarkably similar, and should not be particularly faster one or the other. Denny