From owner-freebsd-hackers Fri Jun 27 00:56:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09938 for hackers-outgoing; Fri, 27 Jun 1997 00:56:46 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA09932 for ; Fri, 27 Jun 1997 00:56:41 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id RAA17175; Fri, 27 Jun 1997 17:41:08 +1000 Date: Fri, 27 Jun 1997 17:41:08 +1000 From: Bruce Evans Message-Id: <199706270741.RAA17175@godzilla.zeta.org.au> To: bmcgover@cisco.com, hackers@freebsd.org Subject: Re: Clists limited to 1024 bytes? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >It appears that l_rint will stop passing characters up at 19200 at around 1K >(or so t_rawq.cc states). Is there any way to safely increase this to around >8K, or even 16K? The reason I ask is that the board I'm working with has an No simple way. >8K receive buffer, and I'd like (for the sake of efficiency), be able to move >nearly a full buffer of data at once, but I seem to be limited by this number. You don't want to do this. At 19200 bps, an 8K buffer takes more than 4 seconds to fill. A latency of 4 seconds is normally about 400 times too large. At such a low speed, there is normally nothing better than delivering input in tiny bursts of 19-20 characters every 10 msec. Bruce