uucp over terminal server

[Gregory N. Bond]

In article <91705 at pyramid.pyramid.com> romain at pyramid.pyramid.com (Romain Kang) writes:

   The potential disadvantage that I see is that the pkcget() stall code
   in 4.3 uucp or the VMIN termio setting in HDB aren't applicable to
   non-tty descriptors like sockets, which may make the kernel schedule
   uucico more frequently than optimal.  In other words, uucico could
   spin on reads that only return a few characters at a time, rather
   than pulling in (nearly) complete 'g' packets on each read.

Except that, at least in our Bridge CS-100 terminal server, you can
specify a buffer size, and (up to, depending on timeouts) that many
characters get buffered up and sent in one TCP packet.  Thus the read
on the socket gets a buffer full.

A second advantage is that our terminal server does RTS-CTS flow
control with the blazer, and is happy doing 19,200baud, that the SunOs
3.5 driver can't.  Given an 8-bit datapath and protocols to take
advantage of it, that is a big win.

We found that, using the terminal server, the NNdaemon (the moral
equivalent of uucico for the networking software mainly used in
Australia) dropped from >50% CPU to < 0.5%, while the speed increased
from 600bytes/sec to >800bytes/sec.

Greg.
--
Gregory Bond, Burdett Buckeridge & Young Ltd, Melbourne, Australia
Internet: gnb at melba.bby.oz.au    non-MX: gnb%melba.bby.oz at uunet.uu.net
Uucp: {uunet,pyramid,ubc-cs,ukc,mcvax,prlb2,nttlab...}!munnari!melba.bby.oz!gnb