From owner-freebsd-hackers Mon Dec 6 12:58:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 430E515ABA; Mon, 6 Dec 1999 12:56:16 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA38267; Mon, 6 Dec 1999 13:56:15 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA36534; Mon, 6 Dec 1999 13:56:15 -0700 (MST) Message-Id: <199912062056.NAA36534@harmony.village.org> To: Mike Smith Subject: Re: tty level buffer overflows Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 06 Dec 1999 11:53:43 PST." <199912061953.LAA00484@mass.cdrom.com> References: <199912061953.LAA00484@mass.cdrom.com> Date: Mon, 06 Dec 1999 13:56:15 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912061953.LAA00484@mass.cdrom.com> Mike Smith writes: : Growing the buffer isn't the solution; it should be big enough already. : We need to work out why a system that should have no trouble with the : data rate in question is croaking so trivially. Growing the buffer is a solution. I only get a few of these very rarely which tells me that the system is keeping up 99.999% of the time. Increasing the buffer size will, statistically speaking, increase that by another .0009%, which is all I'm looking for. Growing the buffer will allow the amont of latency in the worst case to expand, which is what I want. Also, it will work around the problem until I can get a better solution.... At least for my setup. I have a 486DX2-66 with lots of filter rules. I suspect that what is happening is lots of tiny packets are coming in which is causing increased latency in some cases. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message