From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 14:25:24 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEE8137B401 for ; Thu, 3 Jul 2003 14:25:24 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8940E43F93 for ; Thu, 3 Jul 2003 14:25:22 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h63LPIE1040351; Thu, 3 Jul 2003 15:25:19 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 03 Jul 2003 15:25:12 -0600 (MDT) Message-Id: <20030703.152512.91778368.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <20030703102627.D92002@root.org> References: <20030701164231.M88547@root.org> <20030703.052315.32736625.imp@bsdimp.com> <20030703102627.D92002@root.org> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: acpi-jp@jp.freebsd.org cc: current@freebsd.org Subject: Re: Updated ec-burst.diff patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2003 21:25:25 -0000 In message: <20030703102627.D92002@root.org> Nate Lawson writes: : On Thu, 3 Jul 2003, M. Warner Losh wrote: : > In message: <20030701164231.M88547@root.org> : > Nate Lawson writes: : > : On Wed, 2 Jul 2003, Florian Smeets wrote: : > : > I set hw.acpi.ec.burst_mode=0 in loader.conf but when i was trying to : > : > chek if it was set to 0 with sysctl hw.acpi.ec.burst_mode i got : : > : > : > : > flo@lappi [~] 15 #sysctl hw.acpi.ec.burst_mode : > : > sysctl: unknown oid 'hw.acpi.ec.burst_mode' : > : : > : It's a tunable, not a sysctl. So you can only set it in loader.conf. Are : > : there any messages when you boot with that in your loader.conf? Would you : > : please post a separate dmesg for that case? : > : > I personally think that all tunable should be read-only (or rw if : > possible) sysctls... : : I'm still not sure why we have both mechanisms. Perhaps a useful approach : would be to sweep the tree for tunables and change them to sysctls with : appropriate permissions (read-only if in doubt). Then remove the tunable : mechanism. Care to put together a patch? We have both mechanisms because there are a number of things in sysctl that just do not make sense to be a tunable. For example, the number of packets transmitted, or the memory usage string aren't good for this. We have three classes here: 1) things that must be set early in boot sequence and are then read-only. 2) Things that can be set in boot process, but also changed later. 3) Things that are initialized to the same value all the time, and only changed from time to time based on events happening in the system. Tunables are #1. tunables + sysctl are number 2 (although there are a large number of sysctls that could be tunables but aren't for historical reasons). Sysctl for #3 make up the vast bulk of things. So it wouldn't quite so easy to do... However, if you can deal with these, then it might not be a bad idea. Warner