Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site nrcvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!ittatc!dcdwest!sdcsvax!sdcrdcf!psivax!nrcvax!jt
From: jt@nrcvax.UUCP (Jerry Toporek)
Newsgroups: net.unix-wizards,net.lan
Subject: Re: CPU usage of telnetd
Message-ID: <572@nrcvax.UUCP>
Date: Sun, 16-Mar-86 17:40:07 EST
Article-I.D.: nrcvax.572
Posted: Sun Mar 16 17:40:07 1986
Date-Received: Wed, 19-Mar-86 00:49:45 EST
References: <10620@amdcad.UUCP>
Reply-To: jt@nrcvax.UUCP (Jerry Toporek)
Organization: Network Research Research Corp.  Oxnard,CA
Lines: 39
Xref: watmath net.unix-wizards:17256 net.lan:1356

In article <10620@amdcad.UUCP> phil@amdcad.UUCP (Phil Ngai) writes:
>There's a vendor who wants to sell me an ethernet interface that looks
>like a DMF serial interface. (actually, there's several of them) They
>claim telnetd uses a lot of resources. I was dubious but then I used
>the 'top' utility and saw a telnetd doing continous output at an
>effective rate of 9600 baud uses 20% of a 780.
>
>It sounds like the vendor is right. Any comments? Are there any
>implementations of telnetd which are more efficient or is this just
>inherent in the nature of the system?

Phil:

I don't know if you are referencing our product or not, but from the des-
cription you certainly might be.

If the telnet daemon is intended to extensively inspect both the input and
output streams, then resource utilization such as you describe might occur.
Our net terminal driver looks like a DMF only in the sense that it interfaces
with the VMS terminal class handler just like a DMF, or DZ, or whatever.  The
telnet daemon in this sort of setup is not required to do any input or output
processing, that is all left to the class handler.  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.
We still route keyboard input through the daemon, since there are a few things
we want to handle there, like urgent data.)  In this configuration, the test
you mention above, monitoring a continuous output to the net terminal, should
show resource utilization by the daemon of 0.

jt

-- 
=========================    `` ''    ====================================
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