From owner-freebsd-current@FreeBSD.ORG Mon Nov 24 19:17:26 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 2A6C216A4CF for ; Mon, 24 Nov 2003 19:17:26 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8676743FA3 for ; Mon, 24 Nov 2003 19:17:24 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id hAP3HN5g008908 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 24 Nov 2003 22:17:24 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id hAP3HI019653; Mon, 24 Nov 2003 22:17:18 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16322.51646.766041.349180@grasshopper.cs.duke.edu> Date: Mon, 24 Nov 2003 22:17:18 -0500 (EST) To: freebsd-current@freebsd.org In-Reply-To: <20031125025621.453732A8FC@canning.wemm.org> References: <20031124.191931.67791612.imp@bsdimp.com> <20031125025621.453732A8FC@canning.wemm.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Subject: Re: 40% slowdown with dynamic /bin/sh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2003 03:17:26 -0000 Peter Wemm writes: > We need nsswitch type functionality in /bin/sh. To the people who want to > make it static, lets see some static binary dlopen() support or a nsswitch > proxy system. Maybe this is just nieve, but I always thought that it was the responsibility of the party introducing the creeping feature to underdatand and then minimize a potential performance impact. But now we're treading over ground brought up by John Dyson last week. I've at least partially quantified the performance impact, which is all I have time for. Drew