Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!lll-crg!lll-lcc!qantel!hplabs!sdcrdcf!psivax!nrcvax!jt
From: jt@nrcvax.UUCP (Jerry Toporek)
Newsgroups: net.unix-wizards,net.lan
Subject: Re: CPU usage of telnetd
Message-ID: <601@nrcvax.UUCP>
Date: Thu, 27-Mar-86 15:47:40 EST
Article-I.D.: nrcvax.601
Posted: Thu Mar 27 15:47:40 1986
Date-Received: Sun, 20-Apr-86 15:32:14 EST
References: <10620@amdcad.UUCP> <572@nrcvax.UUCP> <11048@amdcad.UUCP>
Reply-To: jt@nrcvax.UUCP (Jerry Toporek)
Organization: Network Research Research Corp.  Oxnard,CA
Lines: 21

In article <11048@amdcad.UUCP> phil@amdcad.UUCP (Phil Ngai) writes:
>In article <572@nrcvax.UUCP> jt@nrcvax.UUCP (Jerry Toporek) writes:
>>In this case a good bit of
>>resource can be wasted passing off output to the telnet daemon to pass onn to
>>the net.  (This is what we were doing in our initial version.)  This can be
>>improved upon by arranging to pass data received by the terminal driver from
>>the class handler directly to the network driver.  (This is what we now do.
>
>This sounds like a good idea. Can you make Unix do this too?

Well, I don't know much about driver to driver communication under Unix.  When
you mentioned the DMF lookalike I thought you were probably talking about VMS
since the usual trick for doing a net tty driver on VMS is to "look like" a
real device.

-- 
=========================    `` ''    ====================================
Jerry Toporek               <`@-@'>             Network Research Corp.
ihnp4!nrcvax!jt              ( > )              1620 Federal Ave. Suite #2
ucbvax!calma!nrcvax!jt        \~/               LA, CA, 90025, USA
{sdcsvax,hplabs}!sdcrdcf!psivax!nrcvax!jt       (213) 479-6436