From owner-freebsd-arch Sun Jul 14 2:54:31 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 323F737B400 for ; Sun, 14 Jul 2002 02:54:27 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEDFE43E67 for ; Sun, 14 Jul 2002 02:54:26 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g6E9sBwr020599; Sun, 14 Jul 2002 02:54:15 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200207140954.g6E9sBwr020599@gw.catspoiler.org> Date: Sun, 14 Jul 2002 02:54:11 -0700 (PDT) From: Don Lewis Subject: Re: wiring the sysctl output buffer To: phk@critter.freebsd.dk Cc: arch@FreeBSD.ORG In-Reply-To: <51318.1026638915@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 14 Jul, Poul-Henning Kamp wrote: > In message <200207140916.g6E9Ghwr020552@gw.catspoiler.org>, Don Lewis writes: > >>I think the best solution to this problem is to add a sysctl system API >>to prewire the output buffer that can be called before grabbing the >>locks. Doing so allows the existing code to operate properly with only >>minimal changes. > > It used to be that sysctl unconditionally wired the output buffer, > but that gave rise to a host of other problems. Anything specific that I should be aware of? > I'm not against the suggested change, but it should be used with > caution. I'd only want to use this when it was the best solution, preferably after checking that SYSCTL_OUT() would actually be called. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message