From owner-freebsd-net Tue Dec 15 09:42:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26117 for freebsd-net-outgoing; Tue, 15 Dec 1998 09:42:49 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from netrinsics.com ([202.99.61.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26086; Tue, 15 Dec 1998 09:42:37 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id BAA02158; Wed, 16 Dec 1998 01:39:17 GMT (envelope-from robinson) Date: Wed, 16 Dec 1998 01:39:17 GMT From: Michael Robinson Message-Id: <199812160139.BAA02158@netrinsics.com> To: fenner@parc.xerox.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <98Dec15.085714pst.177535@crevenia.parc.xerox.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Fenner writes: >>Is there any documentation on why MINCLSIZE is currently set to the value it >>is? > >Not that I know of, but I can't say for sure that there's not something >in the 4.4 daemon book. You know what the main tradeoff is of reducing >MINCLSIZE (and there are some subtle ones too - set your socket buffer >to 64k and start writing in 120-byte chunks and see when the socket >buffer fills up). Well, I just discovered another interesting effect of the smaller MINCLSIZE. After exhaustive testing with the standard X benchmarking utility (xmame), I've discovered a significant performance improvement for graphics- intensive X applications. -Michael Robinson P.S. It may be a while before I get around to testing your "short" patch ;-). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message