Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!rutgers!mcdchg!laidbak!botton
From: botton@i88.isc.com (Brian D. Botton)
Newsgroups: comp.sys.3b1
Subject: Re: 19.2K on a 3b1
Message-ID: <1991Apr5.054939.4239@i88.isc.com>
Date: 5 Apr 91 05:49:39 GMT
References: <2214@public.BTR.COM> <1991Mar27.033750.29895@ceilidh.beartrack.com> <1991Apr04.144939.587@quest.UUCP>
Sender: usenet@i88.isc.com (Usenet News)
Distribution: na
Organization: INTERACTIVE Systems Corporation, Naperville, IL
Lines: 52
Nntp-Posting-Host: laitnite.i88.isc.com

In article <1991Apr04.144939.587@quest.UUCP> ssb@quest.UUCP (Scott Bertilson) writes:

  [ stuff deleted ]

>have to run the terminal manager under MGR.  Someone suggested that
>MGR was too CPU-intensive to run a terminal emulator, so my second
>test was to "Suspd" myself to another "wind.o" window and run the
>terminal emulator..which normally shuts down MGR and drops you into
>a shell in the window you left.  That worked just fine . . . . .

  Brad and I found out about this a couple of months ago, and Brad has
been too busy to really look into it.

  [ more stuff deleted ]

>  I don't know that much about the internals of MGR, but I
>am inclined strongly to believe that the only thing it is
>doing when "idle" but alive is calling "select".

  The select call does indeed seem to be the problem, but at least
you have source so you can investigate instead of speculate.

>						   I'm
>convinced that somewhere in "select" there is a long critical
>section run with interrupts blocked, but I can't figure out
>where it is.

  I'm sure Brad wouldn't mind it if you should happen to find the problem
and fix it.

>		The fact that Ethernet exhibits the same symptoms
>leads me to believe that this is an insurmountable problem
>inherent in applying the "select" wart to our SysV hog.  (I
>assume that BSD on VAXen solves it using the NETISR code,
>but I haven't had access to BSD kernel source for a number
>of years so I can't see how they make "select" work better.)

  The code for select was based on code from the person that did the
TCP/IP port and from the BSD 4.3 select code.

>I've wondered if one might be able to solve this problem by
>carefully applied optimizations to "select", but I don't know
>what part of the code to concentrate on and haven't had time
>to experiment until I figured out.

  You're not alone.  Good hunting.

--
     ...     ___	     ***
   _][_n_n___i_i ________  *******		Brian D. Botton
  (____________I_I______I_I_______I		laidbak!botton  or
  /ooOOOO OOOOoo  oo oooo  oo   oo		laidbak!bilbo!brian