From owner-freebsd-current Thu Mar 9 12:21:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA21181 for current-outgoing; Thu, 9 Mar 1995 12:21:22 -0800 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA21174 for ; Thu, 9 Mar 1995 12:21:19 -0800 Received: by pelican.com (Smail3.1.28.1 #5) id m0rmohr-000K3UC; Thu, 9 Mar 95 12:21 WET Message-Id: Date: Thu, 9 Mar 95 12:21 WET From: pete@pelican.com (Pete Carah) To: jhs@regent.e-technik.tu-muenchen.de Subject: Re: bad outgoing serial coms In-Reply-To: <199503091625.RAA03532@vector.enet> Organization: Pelican Consulting Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk In article <199503091625.RAA03532@vector.enet> you write: >I have recently been seeing a lot of: > vector kernel.old: sio3: 110 more tty-level buffer overflows (total 220) This goes in /usr/src/sys/sys/tty.h. Make TTYHOG big - one friend of mine needs 10240 and another 8192. It could need to be as big as Taylor's i-protocol window which is 16384 (if your problem is with uucp). If you are using another protocol, TTYHOG may need to be as big as the TCP window plus the overhead; this probably defaults to 4096 or 8192. We need to figure out better clist handling for the 'advanced' protocols, or dynamic clist limits. The default (512) is fine for the default uucp protocol of g/3*64 but not much more (barely for g/7*64). Unfortunately making TTYHOG big allocates this much for EVERY tty-style open; interactive sessions don't need it. Just a waste of kernel malloc space :-) -- Pete