From owner-freebsd-hackers Tue Nov 28 09:36:29 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA20987 for hackers-outgoing; Tue, 28 Nov 1995 09:36:29 -0800 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA20982 for ; Tue, 28 Nov 1995 09:36:26 -0800 Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA12747; Tue, 28 Nov 1995 11:35:48 -0600 From: Joe Greco Message-Id: <199511281735.LAA12747@brasil.moneng.mei.com> Subject: Re: 3940? To: bde@zeta.org.au (Bruce Evans) Date: Tue, 28 Nov 1995 11:35:47 -0600 (CST) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <199511280911.UAA20911@godzilla.zeta.org.au> from "Bruce Evans" at Nov 28, 95 08:11:23 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org Precedence: bulk > >Related, but not really: pet peeve of the day: DK_NDRIVE is set to 8 in > >sys/dkstat.h. This effectively limits the number of drives I can get > >statistics on - statistics that would tend to be more useful the more drives > >I have. Is there any harm in increasing this? My news box has a dozen > >disks. > > I think you're supposed to increase it if you have a lot of disks. Don't > forget to recompile all utilities that depend on it. Okay, thanks, I suppose I can bust my news server trying this out :-) I started looking into this when I noticed some brokenness w.r.t. systat and other utilities, there are other deficiencies as well out in userland (systat/etc try to display device names as "sd" and a single digit, doesn't work at large sites :-) ) which I had been intending to patch and submit, but it wasn't really worth my time if it wasn't able to display "interesting" disks!! > >(I also noticed: extern int dk_busy; /* bit field of busy drives */ > >which is sorta scary :-) wonder how many other places there are hidden > >limits built in?) > > dk_busy is only supported by the wd driver. I guess that's why the msps > field in systat only sort of works for wd drives. DK_NDRIVE must be > less than the number of bits in an int for dk_busy to work right. I > think most of the limits are explicit (like DK_NDRIVE). Of course, > this is the wrong way to do things. Ecccch. :-) Thank you for the background and information... very helpful. ;-) ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847