From owner-cvs-all  Mon Nov 29 14:34:46 1999
Delivered-To: cvs-all@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP
	id 07A7A1553E; Mon, 29 Nov 1999 14:34:40 -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 PAA06036;
	Mon, 29 Nov 1999 15:34:39 -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 PAA97412; Mon, 29 Nov 1999 15:35:06 -0700 (MST)
Message-Id: <199911292235.PAA97412@harmony.village.org>
To: Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: cvs commit: src/sys/i386/conf files.i386 src/sys/kern kern_fork.c src/sys/libkern arc4random.c src/sys/sys libkern.h 
Cc: Dan Moschuk <dan@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG,
	cvs-all@FreeBSD.ORG
In-reply-to: Your message of "Mon, 29 Nov 1999 14:21:54 PST."
		<199911292221.OAA11475@apollo.backplane.com> 
References: <199911292221.OAA11475@apollo.backplane.com>  <199911292202.OAA09817@apollo.backplane.com> <19991129161327.E2999@spirit.jaded.net> <199911281751.JAA40710@freefall.freebsd.org> <199911292104.NAA09106@apollo.backplane.com> <199911292200.PAA95264@harmony.village.org> <199911292214.PAA97196@harmony.village.org> 
Date: Mon, 29 Nov 1999 15:35:06 -0700
From: Warner Losh <imp@village.org>
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

In message <199911292221.OAA11475@apollo.backplane.com> Matthew Dillon writes:
:     I'm not sure I understand your comments in regards to NFS.  NFS is
:     optionable (and for BOOTP to work it's required, obviously).

NFS is on the install boot disk.  Some minor efforts on nfs could
result in a savings of more than 686 bytes.  We'd get a larger bang
for the buck loading the firmware for drivers, reducing the verbosity
of messages, etc.

It is already controlled by a sysctl variable.

We're at the level where > 1k should be the threshold.  Many changes
in the kernel have > 1k.  look at kern_ntptime.o.  It is approx 2.5k,
but not optional.  Other example could be found in that same size
range (or bigger, look at the kernel linker at 6k)...  That's the
point I'm trying to make.  There are bigger poles in this tent and we
have't been good about marking the poles, nor in establishing policy
for compile time vs runtime engineering decisions.

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message